Skip to content

[Snyk] Fix for 4 vulnerabilities #11554

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 #11554

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/apache-airflow/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,8 +22,8 @@
"clean": "backstage-cli package clean"
},
"dependencies": {
"@backstage/core-components": "workspace:^",
"@backstage/core-plugin-api": "workspace:^",
"@backstage/core-components": "0.8.6",
"@backstage/core-plugin-api": "0.1.0",
Comment on lines +25 to +26
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 introduce a significant downgrade of core Backstage packages. The versions are being pinned to very old releases (0.8.6 and 0.1.0), while the rest of the monorepo uses much newer versions (@backstage/core-components@0.13.4-next.0 and @backstage/core-plugin-api@1.5.3).

Using workspace:^ ensures that packages within the monorepo use compatible versions from the same workspace. Replacing this with hard-coded old versions will almost certainly lead to build failures, runtime errors, and API incompatibilities.

This automated change by Snyk seems incorrect for this monorepo structure. The vulnerabilities should be addressed without breaking the dependency management of the project. It's recommended to revert these changes and investigate a proper fix, for example by using resolutions in package.json to force a specific version of the vulnerable transitive dependency.

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

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