Skip to content
Open
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
6 changes: 3 additions & 3 deletions plugins/catalog-backend-module-unprocessed/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -28,9 +28,9 @@
"dist"
],
"dependencies": {
"@backstage/backend-plugin-api": "workspace:^",
"@backstage/catalog-model": "workspace:^",
"@backstage/plugin-auth-node": "workspace:^",
"@backstage/backend-plugin-api": "1.6.1",
"@backstage/catalog-model": "0.1.1",
"@backstage/plugin-auth-node": "0.6.0",
Comment on lines +31 to +33

Choose a reason for hiding this comment

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

critical

These changes, which replace workspace:^ with pinned versions, are incorrect for this monorepo setup and will likely break the project. The workspace: protocol is intentionally used in monorepos to ensure that internal packages use the versions from the local workspace, providing consistency and avoiding version conflicts.

By pinning to specific versions:

  • You lose the benefit of the monorepo's single version policy.
  • It can introduce multiple, conflicting versions of the same package.
  • In this case, it's attempting to downgrade @backstage/catalog-model from version 1.4.1 (in the workspace) to 0.1.1, which is a significant and breaking downgrade.

The correct approach to fix the underlying vulnerabilities is to update the dependencies within the monorepo itself, not to pin versions in consuming packages. These changes should be reverted.

    "@backstage/backend-plugin-api": "workspace:^",
    "@backstage/catalog-model": "workspace:^",
    "@backstage/plugin-auth-node": "workspace:^"

"express-promise-router": "^4.1.1",
"knex": "^2.4.2"
}
Expand Down
Loading