Skip to content

[Snyk] Security upgrade @backstage/plugin-catalog-backend from 0.0.0-use.local to 2.0.0 #5250

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/plugin-catalog-backend from 0.0.0-use.local to 2.0.0 #5250

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 plugins/catalog-backend-module-incremental-ingestion/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@
"@backstage/catalog-model": "workspace:^",
"@backstage/config": "workspace:^",
"@backstage/errors": "workspace:^",
"@backstage/plugin-catalog-backend": "workspace:^",
"@backstage/plugin-catalog-backend": "2.0.0",
Copy link
Copy Markdown

@graphite-app graphite-app Bot May 20, 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 (2.0.0) breaks the monorepo dependency management pattern. This change will likely cause compatibility issues with other Backstage packages that expect consistent versioning through workspace references.

The PR description already indicates that the yarn.lock update failed, which is a warning sign. In Backstage's monorepo architecture, packages should maintain workspace references to ensure proper version alignment during development.

Consider either:

  1. Maintaining the workspace reference pattern (workspace:^)
  2. Updating all related packages consistently if fixed versions are required
  3. Using the Backstage-recommended approach for security updates in monorepos

This change as-is risks breaking the build or creating subtle runtime compatibility issues.

Suggested change
"@backstage/plugin-catalog-backend": "2.0.0",
"@backstage/plugin-catalog-backend": "workspace:^",

Spotted by Diamond

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

"@backstage/plugin-catalog-node": "workspace:^",
"@backstage/plugin-events-node": "workspace:^",
"@backstage/plugin-permission-common": "workspace:^",
Expand Down
Loading