Skip to content

[Snyk] Fix for 3 vulnerabilities #11606

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 3 vulnerabilities #11606

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
8 changes: 4 additions & 4 deletions plugins/catalog-backend-module-bitbucket-cloud/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,14 +47,14 @@
"dependencies": {
"@backstage/backend-common": "workspace:^",
"@backstage/backend-plugin-api": "workspace:^",
"@backstage/backend-tasks": "workspace:^",
"@backstage/backend-tasks": "0.6.1",
"@backstage/catalog-client": "workspace:^",
"@backstage/catalog-model": "workspace:^",
"@backstage/config": "workspace:^",
"@backstage/integration": "workspace:^",
"@backstage/plugin-bitbucket-cloud-common": "workspace:^",
"@backstage/plugin-catalog-common": "workspace:^",
"@backstage/plugin-catalog-node": "workspace:^",
"@backstage/plugin-bitbucket-cloud-common": "0.1.0",
"@backstage/plugin-catalog-common": "0.1.0",
"@backstage/plugin-catalog-node": "1.0.0",
Comment on lines +50 to +57
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 seems to have incorrectly replaced workspace:^ with pinned versions for these dependencies. In a monorepo using workspaces (like Backstage), workspace:^ ensures that the local, in-repo version of the package is used. Changing this to a pinned version will cause these packages to be fetched from the npm registry instead, which can lead to several issues:

  • Inconsistent Dependencies: You may end up with multiple versions of the same package, one from the workspace and one from the registry.
  • Broken Local Development: Changes made to these local packages will not be reflected in this module.
  • Build Failures: This can break singleton patterns and cause type mismatches.

The correct way to resolve the underlying vulnerabilities is likely to update the versions of the packages within the monorepo itself and then run yarn to update the lockfile. It's recommended to revert these changes and handle the dependency updates manually to respect the monorepo structure.

    "@backstage/backend-tasks": "workspace:^",
    "@backstage/catalog-client": "workspace:^",
    "@backstage/catalog-model": "workspace:^",
    "@backstage/config": "workspace:^",
    "@backstage/integration": "workspace:^",
    "@backstage/plugin-bitbucket-cloud-common": "workspace:^",
    "@backstage/plugin-catalog-common": "workspace:^",
    "@backstage/plugin-catalog-node": "workspace:^"

"@backstage/plugin-events-node": "workspace:^",
"uuid": "^8.0.0",
"winston": "^3.2.1"
Expand Down
Loading