Skip to content
Closed
Changes from all commits
Commits
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/git-release-manager/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -23,9 +23,9 @@
"clean": "backstage-cli package clean"
},
"dependencies": {
"@backstage/core-components": "workspace:^",
"@backstage/core-components": "0.1.0",
"@backstage/core-plugin-api": "workspace:^",
"@backstage/integration": "workspace:^",
"@backstage/integration": "0.1.0",
Comment on lines +26 to +28
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

critical

This change incorrectly downgrades @backstage/core-components and @backstage/integration to version 0.1.0. In this monorepo setup, these packages use the workspace:^ protocol to link to the local packages within the workspace.

The current versions in the workspace are significantly newer:

  • @backstage/core-components: 0.13.4-next.0
  • @backstage/integration: 1.5.1

Pinning to 0.1.0 is a major downgrade that will likely cause build failures or runtime errors due to breaking changes between versions. This automated change by Snyk does not correctly handle yarn workspaces. The correct approach is to update the vulnerable transitive dependencies, likely by updating the versions of packages within the monorepo, not by pinning to outdated external versions.

I recommend reverting these changes to use the workspace versions.

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

"@backstage/theme": "workspace:^",
"@material-ui/core": "^4.12.2",
"@material-ui/icons": "^4.9.1",
Expand Down
Loading