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/events-backend-module-azure/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -35,8 +35,8 @@
"postpack": "backstage-cli package postpack"
},
"dependencies": {
"@backstage/backend-plugin-api": "workspace:^",
"@backstage/plugin-events-node": "workspace:^",
"@backstage/backend-plugin-api": "0.6.19",
"@backstage/plugin-events-node": "0.2.9",
Comment on lines +38 to +39
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

Pinning dependencies to specific versions instead of using workspace:^ goes against the conventions of a monorepo using Yarn workspaces. This change will cause this package to fall out of sync with the versions used across the rest of the repository, creating maintenance challenges and potential dependency conflicts.

The recommended approach is to address the vulnerabilities within the source packages (@backstage/backend-plugin-api and @backstage/plugin-events-node) and allow the updates to propagate through the workspace. This maintains a single version policy and simplifies dependency management.

    "@backstage/backend-plugin-api": "workspace:^",
    "@backstage/plugin-events-node": "workspace:^"

"winston": "^3.2.1"
},
"devDependencies": {
Expand Down
Loading