Skip to content

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

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 2 commits into from
Closed

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

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b7864c5
fix: plugins/nomad/package.json to reduce vulnerabilities
snyk-bot Feb 6, 2026
37d1c2e
fix: plugins/nomad/package.json to reduce vulnerabilities
snyk-io[bot] Feb 7, 2026
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/nomad/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@
"@backstage/catalog-model": "workspace:^",
"@backstage/config": "workspace:^",
"@backstage/core-components": "workspace:^",
"@backstage/core-plugin-api": "workspace:^",
"@backstage/core-plugin-api": "0.1.0",
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot Feb 6, 2026

Choose a reason for hiding this comment

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

critical

This change from "workspace:^" to a hardcoded version "0.1.0" is incorrect for this monorepo setup. The workspace: protocol is essential for linking packages within the same Yarn workspace, ensuring consistency and proper local development.

Pinning to a specific version, especially a very outdated one like 0.1.0 (the version in the workspace is 1.5.3), will break dependency resolution and likely cause build or runtime failures. This automated change should be reverted. The underlying security vulnerabilities should be addressed by updating dependencies correctly across the monorepo, which will also allow the yarn.lock file to be updated properly.

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

"@backstage/plugin-catalog-react": "workspace:^",
"@backstage/theme": "workspace:^",
"@material-ui/core": "^4.9.13",
Expand Down
Loading