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
12 changes: 6 additions & 6 deletions plugins/permission-backend/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -37,16 +37,16 @@
"clean": "backstage-cli package clean"
},
"dependencies": {
"@backstage/backend-common": "workspace:^",
"@backstage/backend-plugin-api": "workspace:^",
"@backstage/backend-common": "0.24.1",
"@backstage/backend-plugin-api": "0.6.19",
"@backstage/config": "workspace:^",
"@backstage/errors": "workspace:^",
"@backstage/plugin-auth-node": "workspace:^",
"@backstage/plugin-permission-common": "workspace:^",
"@backstage/plugin-permission-node": "workspace:^",
"@backstage/plugin-auth-node": "0.6.0",
"@backstage/plugin-permission-common": "0.1.0",
"@backstage/plugin-permission-node": "0.1.0",
Comment on lines +40 to +46
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

high

Changing these dependencies from workspace:^ to pinned versions is a significant alteration of the dependency strategy for this monorepo. The workspace: protocol is designed to ensure that packages within the monorepo use the most up-to-date local versions of each other. By pinning to specific published versions, you lose this benefit and risk introducing inconsistencies or using stale code if other packages in the monorepo are updated. It is strongly recommended to resolve the underlying vulnerabilities in a way that preserves the workspace: protocol, for instance by updating the source packages within the monorepo.

"@types/express": "*",
"dataloader": "^2.0.0",
"express": "^4.17.1",
"express": "^4.22.0",
"express-promise-router": "^4.1.0",
"lodash": "^4.17.21",
"node-fetch": "^2.6.7",
Expand Down
Loading