Skip to content

[Snyk] Security upgrade @backstage/types from 0.0.0-use.local to 0.1.1 #11964

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/types from 0.0.0-use.local to 0.1.1 #11964

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-common/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@
"clean": "backstage-cli package clean"
},
"dependencies": {
"@backstage/types": "workspace:^",
"@backstage/types": "0.1.1",

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

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

critical

This automated change is incorrect and should be rejected. It replaces the yarn workspace dependency with a pinned, and much older, version of @backstage/types.

  1. Breaks Workspace Linking: Changing "workspace:^" to "0.1.1" will cause yarn to fetch this package from the npm registry instead of linking to the local @backstage/types package within this monorepo. This is a fundamental change to how dependencies are managed in this project.

  2. Significant Downgrade: The suggested version 0.1.1 is a major downgrade. The local @backstage/types package is at version 1.1.0. This downgrade would likely cause build failures or runtime errors, as tech-insights-common depends on features from newer versions of @backstage/types.

It appears Snyk has misinterpreted the workspace:^ protocol, which is also indicated by the warning in the PR description about failing to update yarn.lock. The vulnerabilities it aims to fix may already be resolved in the 1.1.0 version currently in use via the workspace. This PR should be closed. If vulnerabilities persist, the dependencies of the @backstage/types package should be updated directly.

Suggested change
"@backstage/types": "0.1.1",
"@backstage/types": "workspace:^",

"@types/luxon": "^3.0.0",
"luxon": "^3.0.0"
},
Expand Down
Loading