Skip to content

[Snyk] Fix for 6 vulnerabilities #10703

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

Open
q1blue wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Snyk] Fix for 6 vulnerabilities #10703

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
6 changes: 3 additions & 3 deletions plugins/airbrake-backend/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,9 +22,9 @@
"clean": "backstage-cli package clean"
},
"dependencies": {
"@backstage/backend-common": "workspace:^",
"@backstage/backend-plugin-api": "workspace:^",
"@backstage/config": "workspace:^",
"@backstage/backend-common": "0.25.0",
"@backstage/backend-plugin-api": "1.6.1",
"@backstage/config": "0.1.1",
Comment on lines +25 to +27
Copy link

@gemini-code-assist gemini-code-assist bot Jan 23, 2026

Choose a reason for hiding this comment

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

critical

This automated change from Snyk introduces several critical issues:

  1. Breaks Monorepo Structure: Changing dependencies from workspace:^ to pinned versions decouples this package from the rest of the monorepo. This means it will no longer receive updates when the corresponding workspace packages are updated, leading to maintenance issues and potential inconsistencies.

  2. Major Version Downgrade: The dependency @backstage/config is being pinned to version 0.1.1. However, the version in your workspace (packages/config/package.json) is 1.0.8. This is a significant downgrade that will almost certainly break the airbrake-backend plugin, as it's likely built against a much newer API.

  3. Major Version Upgrades: The other dependencies, @backstage/backend-common and @backstage/backend-plugin-api, are being upgraded to versions (0.25.0 and 1.6.1 respectively) that are much newer than what's in your workspace (0.19.2-next.0 and 0.5.5-next.0). This could also introduce breaking API changes.

It is highly recommended to reject this change. The correct way to fix these vulnerabilities in a monorepo is to update the versions of the packages at the root of the workspace (e.g., in packages/backend-common/package.json). After updating the package versions there, run yarn install to update the yarn.lock file, which should resolve the transitive dependency vulnerabilities.

Given the high risk of breakage, I suggest reverting these changes.

    "@backstage/backend-common": "workspace:^",
    "@backstage/backend-plugin-api": "workspace:^",
    "@backstage/config": "workspace:^"

"@types/express": "*",
"express": "^4.17.1",
"express-promise-router": "^4.1.0",
Expand Down
Loading