Skip to content

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

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

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

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/code-climate/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@
"@backstage/core-components": "workspace:^",
"@backstage/core-plugin-api": "workspace:^",
"@backstage/plugin-catalog-react": "workspace:^",
"@backstage/theme": "workspace:^",
"@backstage/theme": "0.1.1",
Copy link

@gemini-code-assist gemini-code-assist bot Jan 21, 2026

Choose a reason for hiding this comment

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

critical

This change replaces the workspace dependency workspace:^ with a pinned version 0.1.1. This is a significant downgrade, as the version of @backstage/theme within this monorepo is 0.4.1 (as seen in packages/theme/package.json). Using an older, pinned version breaks the integrity of the monorepo, can lead to version mismatches, and may cause runtime errors or unexpected behavior because other parts of the application will be using a different version of the theme.

While this change is intended to fix security vulnerabilities, the correct approach in a monorepo is to update the dependencies within the @backstage/theme package itself or other relevant packages to resolve the vulnerabilities, rather than pinning to an old version of a workspace package.

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

"@material-ui/core": "^4.12.2",
"@material-ui/icons": "^4.9.1",
"@material-ui/lab": "4.0.0-alpha.61",
Expand Down
Loading