Skip to content

[Snyk] Fix for 3 vulnerabilities #11568

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
q1blue wants to merge 1 commit into from
Closed

[Snyk] Fix for 3 vulnerabilities #11568

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/vault-backend/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,10 +33,10 @@
"postpack": "backstage-cli package postpack"
},
"dependencies": {
"@backstage/backend-common": "workspace:^",
"@backstage/backend-tasks": "workspace:^",
"@backstage/backend-common": "0.24.1",
"@backstage/backend-tasks": "0.6.1",
"@backstage/config": "workspace:^",
"@backstage/errors": "workspace:^",
"@backstage/errors": "0.1.1",
Comment on lines +36 to +39
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot Jan 31, 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 replaces workspace:^ with pinned versions for several @backstage packages. This change is problematic in a monorepo environment as it breaks the workspace-based dependency resolution, causing this package to fetch dependencies from the npm registry instead of using local versions from the repository.

This can lead to several issues:

  • Inconsistent versions: Different parts of the application might end up with different versions of the same @backstage library, leading to subtle bugs.
  • Broken development workflow: Local changes to dependencies like @backstage/backend-common will not be reflected when testing plugin-vault-backend.

The PR description notes that yarn.lock failed to update, which strongly suggests this automated approach is incorrect for your project's setup.

The recommended approach is to revert these changes and address the vulnerabilities by updating dependencies across the workspace while preserving the workspace:^ protocol, then regenerating the yarn.lock file.

    "@backstage/backend-common": "workspace:^",
    "@backstage/backend-tasks": "workspace:^",
    "@backstage/config": "workspace:^",
    "@backstage/errors": "workspace:^"

"@types/express": "*",
"compression": "^1.7.4",
"cors": "^2.8.5",
Expand Down
Loading