Skip to content

[Snyk] Security upgrade @backstage/plugin-catalog-common from 0.0.0-use.local to 0.1.0 #4508

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-common from 0.0.0-use.local to 0.1.0 #4508

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-bitbucket-cloud/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@
"@backstage/config": "workspace:^",
"@backstage/integration": "workspace:^",
"@backstage/plugin-bitbucket-cloud-common": "workspace:^",
"@backstage/plugin-catalog-common": "workspace:^",
"@backstage/plugin-catalog-common": "0.1.0",
Copy link
Copy Markdown

@graphite-app graphite-app Bot Apr 2, 2025

Choose a reason for hiding this comment

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

This change introduces a potential dependency conflict in the Backstage monorepo. Replacing the workspace reference (workspace:^) with a pinned version (0.1.0) breaks the monorepo's dependency management pattern and could lead to duplicate package installations.

The PR description also notes that the yarn.lock file wasn't updated successfully, which means the dependency change won't be properly reflected in the dependency tree.

For Backstage monorepos, the recommended approach is to:

  1. Keep the workspace reference syntax (workspace:^)
  2. Update the version in the target package's own package.json
  3. Allow Backstage's monorepo tooling to handle dependency resolution

This ensures consistent versioning across the monorepo while still addressing the security vulnerability.

Suggested change
"@backstage/plugin-catalog-common": "0.1.0",
"@backstage/plugin-catalog-common": "workspace:^",

Spotted by Diamond

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

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