Skip to content

[Snyk] Security upgrade @backstage/backend-common from 0.0.0-use.local to 0.24.1 #5284

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
Closed

[Snyk] Security upgrade @backstage/backend-common from 0.0.0-use.local to 0.24.1 #5284

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
2 changes: 1 addition & 1 deletion packages/backend-tasks/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@
"start": "backstage-cli package start"
},
"dependencies": {
"@backstage/backend-common": "workspace:^",
"@backstage/backend-common": "0.24.1",
Copy link
Copy Markdown

@graphite-app graphite-app Bot Jun 3, 2025

Choose a reason for hiding this comment

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

Replacing a workspace reference (workspace:^) with a fixed version (0.24.1) in a monorepo can create dependency inconsistencies. This change might result in multiple versions of @backstage/backend-common being used across the project, potentially causing unexpected behaviors.

Consider addressing the vulnerability while maintaining the workspace reference structure by:

  1. Updating the shared @backstage/backend-common package within your workspace
  2. Ensuring all packages reference it using workspace:^
  3. Updating the underlying dependencies in the shared package that contain the vulnerability

This approach maintains the monorepo's dependency consistency while still addressing the security issue in tar-fs.

Suggested change
"@backstage/backend-common": "0.24.1",
"@backstage/backend-common": "workspace:^",

Spotted by Diamond

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

"@backstage/config": "workspace:^",
"@backstage/errors": "workspace:^",
"@backstage/types": "workspace:^",
Expand Down
Loading