Skip to content

[Snyk] Fix for 4 vulnerabilities #11557

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] Fix for 4 vulnerabilities #11557

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
4 changes: 2 additions & 2 deletions plugins/shortcuts/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,9 +23,9 @@
"clean": "backstage-cli package clean"
},
"dependencies": {
"@backstage/core-components": "workspace:^",
"@backstage/core-components": "0.8.6",
"@backstage/core-plugin-api": "workspace:^",
"@backstage/theme": "workspace:^",
"@backstage/theme": "0.1.1",
Comment on lines +26 to +28
Copy link

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

Choose a reason for hiding this comment

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

critical

These changes break the yarn workspace setup by replacing workspace:^ with pinned, older versions of @backstage/core-components and @backstage/theme. This will likely cause build failures or runtime issues as other packages in the monorepo expect workspace-local versions.

  • @backstage/core-components is being downgraded from its workspace version (0.13.4-next.0) to 0.8.6.
  • @backstage/theme is being downgraded from its workspace version (0.4.1) to 0.1.1.

The correct approach to fix the vulnerabilities is to identify the vulnerable transitive dependencies within the workspace packages (e.g., @backstage/core-components, @backstage/theme) and update them directly. After updating, run yarn to regenerate the yarn.lock file. It is recommended to revert these changes.

    "@backstage/core-components": "workspace:^",
    "@backstage/core-plugin-api": "workspace:^",
    "@backstage/theme": "workspace:^"

"@backstage/types": "workspace:^",
"@material-ui/core": "^4.12.2",
"@material-ui/icons": "^4.9.1",
Expand Down
Loading