Skip to content

[Snyk] Fix for 6 vulnerabilities #10753

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

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/catalog-graphql/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,9 +36,9 @@
"dependencies": {
"@apollo/client": "^3.0.0",
"@apollo/server": "^4.0.0",
"@backstage/catalog-model": "workspace:^",
"@backstage/catalog-model": "0.1.1",
"@backstage/config": "workspace:^",
"@backstage/types": "workspace:^",
"@backstage/types": "0.1.1",
Comment on lines +39 to +41
Copy link

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

Choose a reason for hiding this comment

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

critical

The Snyk bot has incorrectly modified these dependencies. It has replaced workspace:^ with pinned, outdated versions for @backstage/catalog-model and @backstage/types. This project is a monorepo using yarn workspaces, and this change breaks the workspace linking, forcing the use of old package versions from the registry instead of the local packages from the workspace.

The versions pinned are:

  • @backstage/catalog-model: 0.1.1 (the version in this workspace is 1.4.1)
  • @backstage/types: 0.1.1 (the version in this workspace is 1.1.0)

Using these significantly older versions will likely cause build failures or runtime errors due to API incompatibilities. The PR description also notes that yarn.lock failed to update, which is another indicator of problems.

The correct approach is to revert these changes and address the underlying vulnerabilities, likely by using resolutions in the root package.json to force newer, non-vulnerable versions of the transitive dependencies.

Suggested change
"@backstage/catalog-model": "0.1.1",
"@backstage/config": "workspace:^",
"@backstage/types": "workspace:^",
"@backstage/types": "0.1.1",
"@backstage/catalog-model": "workspace:^",
"@backstage/config": "workspace:^",
"@backstage/types": "workspace:^",

"graphql": "^16.0.0",
"graphql-modules": "^2.0.0",
"graphql-tag": "^2.11.0",
Expand Down
Loading