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 packages/backend/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@
"@backstage/integration": "workspace:^",
"@backstage/plugin-adr-backend": "workspace:^",
"@backstage/plugin-app-backend": "workspace:^",
"@backstage/plugin-auth-backend": "workspace:^",
"@backstage/plugin-auth-backend": "0.1.1",
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

The change from workspace:^ to a fixed version 0.1.1 may disrupt the monorepo's dependency management. The version number 0.1.1 appears unusually low for a Backstage plugin, which typically use higher version numbers. This suggests the version might be incorrect or outdated.

Consider either:

  1. Using a more recent version that addresses the vulnerability
  2. Maintaining the workspace reference and updating the dependency within the workspace

If this PR is addressing the vulnerability correctly, ensure the yarn.lock file is also updated as noted in the warning message.

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.

"@backstage/plugin-auth-node": "workspace:^",
"@backstage/plugin-azure-devops-backend": "workspace:^",
"@backstage/plugin-azure-sites-backend": "workspace:^",
Expand All @@ -51,7 +51,7 @@
"@backstage/plugin-graphql-backend": "workspace:^",
"@backstage/plugin-jenkins-backend": "workspace:^",
"@backstage/plugin-kafka-backend": "workspace:^",
"@backstage/plugin-kubernetes-backend": "workspace:^",
"@backstage/plugin-kubernetes-backend": "0.1.1",
"@backstage/plugin-lighthouse-backend": "workspace:^",
"@backstage/plugin-linguist-backend": "workspace:^",
"@backstage/plugin-nomad-backend": "workspace:^",
Expand Down
Loading