Skip to content

[Snyk] Fix for 6 vulnerabilities #10447

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 6 vulnerabilities #10447

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/graphiql/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,9 +32,9 @@
"clean": "backstage-cli package clean"
},
"dependencies": {
"@backstage/core-components": "workspace:^",
"@backstage/core-components": "0.1.0",
"@backstage/core-plugin-api": "workspace:^",
"@backstage/theme": "workspace:^",
"@backstage/theme": "0.1.1",
Comment on lines +35 to +37
Copy link

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

Choose a reason for hiding this comment

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

critical

These changes incorrectly replace workspace-local dependencies (workspace:^) with fixed, outdated versions from a public registry.

  • @backstage/core-components is pinned to 0.1.0, but the version in this monorepo appears to be 0.13.4-next.0.
  • @backstage/theme is pinned to 0.1.1, but the version in this monorepo appears to be 0.4.1.

This will almost certainly break the build or cause runtime errors due to version mismatches and API incompatibilities. In a monorepo using the workspace: protocol, dependencies should resolve to the packages within the same workspace.

It seems the automated tool failed to resolve the dependencies correctly. These changes should be reverted. To fix the underlying vulnerabilities, you should try to update the dependencies across the entire workspace, which might involve updating @backstage/cli and running a workspace-wide upgrade.

    "@backstage/core-components": "workspace:^",
    "@backstage/core-plugin-api": "workspace:^",
    "@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