Skip to content

[Snyk] Security upgrade @backstage/integration from 0.0.0-use.local to 0.1.0 #5437

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 from 0.0.0-use.local to 0.1.0 #5437

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-issues/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@
"@backstage/core-components": "workspace:^",
"@backstage/core-plugin-api": "workspace:^",
"@backstage/errors": "workspace:^",
"@backstage/integration": "workspace:^",
"@backstage/integration": "0.1.0",
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.

This change replaces the workspace reference with a fixed version, which breaks the monorepo dependency pattern. The other @backstage dependencies use workspace:^ to ensure consistent versioning within the project, while this change pins to a specific version 0.1.0 (which appears to be quite old for Backstage packages).

While addressing security vulnerabilities is important, changing the dependency resolution pattern may introduce other issues:

  1. It creates inconsistency in how dependencies are managed
  2. It may cause version conflicts during dependency resolution
  3. The fixed version might not be compatible with other workspace packages

Consider either:

  • Maintaining the workspace:^ pattern and updating the dependency in the workspace root
  • If a specific version is required for security reasons, verify that 0.1.0 is appropriate and document the exception

The warning about failing to update yarn.lock in the PR description suggests additional manual intervention will be needed before merging.

Suggested change
"@backstage/integration": "0.1.0",
"@backstage/integration": "workspace:^",

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.4",
Expand Down
Loading