Skip to content

[Snyk] Fix for 2 vulnerabilities #12446

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
+6 −6
Closed

[Snyk] Fix for 2 vulnerabilities #12446

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
12 changes: 6 additions & 6 deletions plugins/todo-backend/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,17 +29,17 @@
"start": "backstage-cli package start"
},
"dependencies": {
"@backstage/backend-common": "workspace:^",
"@backstage/backend-openapi-utils": "workspace:^",
"@backstage/backend-common": "0.24.1",
"@backstage/backend-openapi-utils": "0.0.1",
"@backstage/backend-plugin-api": "workspace:^",
"@backstage/catalog-client": "workspace:^",
"@backstage/catalog-model": "workspace:^",
"@backstage/catalog-client": "0.2.0",
"@backstage/catalog-model": "0.1.1",
"@backstage/config": "workspace:^",
"@backstage/errors": "workspace:^",
"@backstage/integration": "workspace:^",
"@backstage/plugin-catalog-node": "workspace:^",
"@backstage/plugin-catalog-node": "1.0.0",
Comment on lines +32 to +40
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot Feb 17, 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 incorrectly replaces workspace:^ dependencies with pinned, published versions. In a Yarn workspace monorepo, this will likely break local development and could lead to having multiple versions of the same Backstage package in the dependency tree. These changes should be rejected.

The vulnerabilities should be addressed manually:

  1. Identify the package in the workspace that has the vulnerable dependency (e.g., for the ajv vulnerability, it's likely @backstage/catalog-model).
  2. Update the vulnerable dependency in that package's package.json.
  3. Run yarn install to update the yarn.lock file.

This will correctly resolve the vulnerability without breaking the workspace setup.

"@types/express": "^4.17.6",
"express": "^4.17.1",
"express": "^4.22.0",
"express-promise-router": "^4.1.0",
"leasot": "^12.0.0",
"winston": "^3.2.1",
Expand Down
Loading