Skip to content

[Snyk] Fix for 1 vulnerabilities #4300

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
snyk-io wants to merge 1 commit into from
+5 −5
Closed

[Snyk] Fix for 1 vulnerabilities #4300

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions plugins/badges-backend/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,13 +33,13 @@
"clean": "backstage-cli package clean"
},
"dependencies": {
"@backstage/backend-common": "workspace:^",
"@backstage/backend-common": "0.24.1",
"@backstage/backend-plugin-api": "workspace:^",
"@backstage/catalog-client": "workspace:^",
"@backstage/catalog-model": "workspace:^",
"@backstage/catalog-client": "0.2.0",
"@backstage/catalog-model": "0.1.1",
"@backstage/config": "workspace:^",
"@backstage/errors": "workspace:^",
"@backstage/plugin-auth-node": "workspace:^",
"@backstage/plugin-auth-node": "0.5.0",
Comment on lines +36 to +42
Copy link
Copy Markdown

@graphite-app graphite-app Bot Mar 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The dependency version changes in this PR won't be effective without corresponding updates to the yarn.lock file. As noted in the PR description warning, the automatic update of yarn.lock failed.

Before merging this security fix PR, the yarn.lock file needs to be manually updated to ensure the vulnerable dependencies are actually replaced with the patched versions. Without this step, the project will continue using the vulnerable packages despite the changes to package.json.

To update the lockfile, run yarn install after these changes and commit the resulting yarn.lock modifications.

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.

"@types/express": "^4.17.6",
"badge-maker": "^3.3.0",
"cors": "^2.8.5",
Expand All @@ -54,7 +54,7 @@
},
"devDependencies": {
"@backstage/backend-test-utils": "workspace:^",
"@backstage/catalog-client": "workspace:^",
"@backstage/catalog-client": "0.2.0",
"@backstage/cli": "workspace:^",
"@types/node": "*",
"cross-fetch": "^3.1.5"
Expand Down
Loading