Skip to content

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

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
snyk-io wants to merge 1 commit into
base: master
Choose a base branch
from
Open

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

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

@graphite-app graphite-app bot Jul 7, 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 with a fixed version (0.1.1) breaks the monorepo's dependency management pattern. This change could lead to version conflicts with other packages that expect to use the same workspace-managed version of @backstage/catalog-model.

Additionally, the PR description indicates that the yarn.lock file failed to update, which must be resolved before merging.

Consider either:

  1. Updating all instances of this package throughout the monorepo to the same version
  2. Maintaining the workspace reference and updating the package version in the root package.json instead

This approach would preserve compatibility while addressing the security vulnerability.

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/plugin-tech-insights-common": "workspace:^",
Expand Down
Loading