Skip to content

[Snyk] Security upgrade @backstage/integration-react from 0.0.0-use.local to 0.1.1 #5628

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] Security upgrade @backstage/integration-react from 0.0.0-use.local to 0.1.1 #5628

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
2 changes: 1 addition & 1 deletion plugins/github-deployments/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@
"@backstage/core-plugin-api": "workspace:^",
"@backstage/errors": "workspace:^",
"@backstage/integration": "workspace:^",
"@backstage/integration-react": "workspace:^",
"@backstage/integration-react": "0.1.1",
Copy link
Copy Markdown

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

Choose a reason for hiding this comment

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

Replacing a workspace dependency with a fixed version (0.1.1) breaks the workspace resolution pattern used throughout the project. This approach:

  1. Creates potential compatibility issues with other Backstage packages that expect consistent versioning
  2. May introduce runtime errors if version 0.1.1 is incompatible with other dependencies
  3. Is incomplete without corresponding yarn.lock updates (which failed according to the PR description)

For security upgrades, consider updating the vulnerable dependency within the workspace pattern instead, maintaining workspace:^ while ensuring the resolved version addresses the vulnerabilities. This preserves the project's dependency management approach while fixing the security issues.

Spotted by Diamond

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

"@backstage/plugin-catalog-react": "workspace:^",
"@backstage/theme": "workspace:^",
"@material-ui/core": "^4.12.2",
Expand Down
Loading