Skip to content

[Snyk] Fix for 4 vulnerabilities #11889

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

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
6 changes: 3 additions & 3 deletions packages/techdocs-cli/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,11 +60,11 @@
"ext": "ts"
},
"dependencies": {
"@backstage/backend-common": "workspace:^",
"@backstage/backend-common": "0.24.1",
"@backstage/catalog-model": "workspace:^",
"@backstage/cli-common": "workspace:^",
"@backstage/config": "workspace:^",
"@backstage/plugin-techdocs-node": "workspace:^",
"@backstage/config": "0.1.1",
"@backstage/plugin-techdocs-node": "1.13.11",
Comment on lines +63 to +67
Copy link

@gemini-code-assist gemini-code-assist bot Feb 7, 2026

Choose a reason for hiding this comment

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

critical

These automated dependency updates from Snyk appear to be incorrect for this monorepo setup. Pinning versions instead of using workspace:^ can break the local development workflow and lead to inconsistencies.

Most critically, the version for @backstage/config is being downgraded from 1.0.8 to 0.1.1, which will almost certainly cause build failures or runtime errors.

The PR description also notes that it Failed to update the yarn.lock, which further indicates these changes are incomplete and require manual review.

It is strongly recommended to revert these changes. The security vulnerabilities should be addressed by correctly updating the package versions within the workspace, rather than applying these automated, and in this case incorrect, changes.

    "@backstage/backend-common": "workspace:^",
    "@backstage/catalog-model": "workspace:^",
    "@backstage/cli-common": "workspace:^",
    "@backstage/config": "workspace:^",
    "@backstage/plugin-techdocs-node": "workspace:^"

"@types/dockerode": "^3.3.0",
"commander": "^9.1.0",
"dockerode": "^3.3.1",
Expand Down
Loading