Skip to content

[Snyk] Security upgrade @backstage/core-plugin-api from 0.0.0-use.local to 0.1.0 #5380

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/core-plugin-api from 0.0.0-use.local to 0.1.0 #5380

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/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@
"@backstage/catalog-client": "workspace:^",
"@backstage/catalog-model": "workspace:^",
"@backstage/core-components": "workspace:^",
"@backstage/core-plugin-api": "workspace:^",
"@backstage/core-plugin-api": "0.1.0",
Copy link
Copy Markdown

@graphite-app graphite-app Bot Jun 4, 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 dependency inconsistency by replacing the workspace reference (workspace:^) with a fixed version (0.1.0) for @backstage/core-plugin-api. All other Backstage packages in this file use workspace references, which ensures consistent versioning across the monorepo.

Using mixed dependency styles can lead to:

  • Version conflicts during dependency resolution
  • Potential runtime errors from mismatched package versions
  • Complications during future upgrades

To maintain consistency, either:

  1. Keep using workspace:^ for all Backstage dependencies (recommended for monorepo development)
  2. Convert all Backstage dependencies to specific versions if there's a strategic reason

Consider addressing the vulnerability through a different approach that preserves the workspace reference pattern.

Suggested change
"@backstage/core-plugin-api": "0.1.0",
"@backstage/core-plugin-api": "workspace:^",

Spotted by Diamond

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

"@backstage/errors": "workspace:^",
"@backstage/integration-react": "workspace:^",
"@backstage/plugin-catalog-common": "workspace:^",
Expand Down
Loading