Skip to content

[Snyk] Fix for 1 vulnerabilities #5406

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
snyk-io wants to merge 1 commit into from
Closed

[Snyk] Fix for 1 vulnerabilities #5406

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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/permission-common/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,9 +41,9 @@
"url": "https://github.com/backstage/backstage/issues"
},
"dependencies": {
"@backstage/config": "workspace:^",
"@backstage/config": "0.1.1",
"@backstage/errors": "workspace:^",
"@backstage/types": "workspace:^",
"@backstage/types": "0.1.1",
Comment on lines +44 to +46
Copy link
Copy Markdown

@graphite-app graphite-app Bot Jun 4, 2025

Choose a reason for hiding this comment

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

Replacing workspace:^ references with fixed versions (0.1.1) breaks the monorepo's workspace dependency pattern, which can lead to:

  1. Package duplication in the dependency tree
  2. Version mismatches between components
  3. Potential compatibility issues with other parts of the codebase

This approach addresses the vulnerability but introduces architectural inconsistency. Consider either:

  • Updating the vulnerable dependency while maintaining the workspace references
  • Using a more recent version that addresses the vulnerability
  • Applying a targeted patch rather than changing the dependency structure

The warning about failing to update yarn.lock in the PR description further suggests this approach may cause integration problems.

Spotted by Diamond

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

"cross-fetch": "^3.1.5",
"uuid": "^8.0.0",
"zod": "^3.21.4"
Expand Down
Loading