Skip to content

[Snyk] Fix for 4 vulnerabilities #11596

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

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/apollo-explorer/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,9 +23,9 @@
},
"dependencies": {
"@apollo/explorer": "^2.0.0",
"@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
Copy Markdown

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

Choose a reason for hiding this comment

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

critical

This automated change from Snyk incorrectly modifies the dependency management for this monorepo. By replacing workspace:^ with pinned, outdated versions, it breaks the yarn workspace linking. This will cause packages to be fetched from the npm registry instead of using the local versions within this repository, likely leading to build failures and runtime errors.

The versions 0.8.6 for @backstage/core-components and 0.1.1 for @backstage/theme are severe downgrades. For context, the versions of these packages within this repository appear to be 0.13.4-next.0 and 0.4.1 respectively.

This change should be reverted. The underlying security vulnerabilities should be addressed by updating the dependencies that introduce them and then running yarn to update the yarn.lock file.

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

"@material-ui/core": "^4.12.2",
"@material-ui/icons": "^4.9.1",
"react-use": "^17.2.4",
Expand Down
Loading