Skip to content

[Snyk] Security upgrade @backstage/catalog-model from 0.0.0-use.local to 0.1.1 #5233

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] Security upgrade @backstage/catalog-model from 0.0.0-use.local to 0.1.1 #5233

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-azure/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@
"@backstage/backend-common": "workspace:^",
"@backstage/backend-plugin-api": "workspace:^",
"@backstage/backend-tasks": "workspace:^",
"@backstage/catalog-model": "workspace:^",
"@backstage/catalog-model": "0.1.1",
Copy link
Copy Markdown

@graphite-app graphite-app Bot May 17, 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.1.1) breaks the monorepo dependency management pattern. This approach may address the security vulnerability but creates potential compatibility issues with other packages that expect the workspace version.

A more sustainable solution would be to:

  1. Update the vulnerable dependency within your workspace version
  2. Ensure the fix propagates through the workspace references

If you must pin to a specific version, coordinate updates across all related packages to maintain consistency. The warning about manual yarn.lock updates in the PR description further suggests this change requires additional work to integrate properly.

Suggested change
"@backstage/catalog-model": "0.1.1",
"@backstage/catalog-model": "workspace:^",

Spotted by Diamond

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

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