[Snyk] Security upgrade @backstage/core-plugin-api from 0.0.0-use.local to 0.1.0#5380
[Snyk] Security upgrade @backstage/core-plugin-api from 0.0.0-use.local to 0.1.0#5380
Conversation
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-TARFS-10293725
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
Reviewer's GuideUpgrades @backstage/core-plugin-api to version 0.1.0 in the catalog plugin to remediate a high-severity TarFS vulnerability, replacing the workspace reference and flagging manual yarn.lock synchronization. State Diagram: @backstage/core-plugin-api Version Transition in Catalog PluginstateDiagram-v2
direction LR
state "workspace:^" as OldVersion
state "0.1.0" as NewVersion
[*] --> OldVersion : Original version in plugins/catalog
OldVersion --> NewVersion : Upgraded by Snyk
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
🎉 Snyk checks have passed. No issues have been found so far.✅ security/snyk check is complete. No issues have been found. (View Details) |
![graphite-app[bot]](https://avatars.githubusercontent.com/in/158384?s=60&v=4){kind=small}
| "@backstage/catalog-model": "workspace:^", | ||
| "@backstage/core-components": "workspace:^", | ||
| "@backstage/core-plugin-api": "workspace:^", | ||
| "@backstage/core-plugin-api": "0.1.0", |
There was a problem hiding this comment.
This change introduces a dependency inconsistency by replacing the workspace reference (workspace:^) with a fixed version (0.1.0) for @backstage/core-plugin-api. All other Backstage packages in this file use workspace references, which ensures consistent versioning across the monorepo.
Using mixed dependency styles can lead to:
- Version conflicts during dependency resolution
- Potential runtime errors from mismatched package versions
- Complications during future upgrades
To maintain consistency, either:
- Keep using
workspace:^for all Backstage dependencies (recommended for monorepo development) - Convert all Backstage dependencies to specific versions if there's a strategic reason
Consider addressing the vulnerability through a different approach that preserves the workspace reference pattern.
| "@backstage/core-plugin-api": "0.1.0", | |
| "@backstage/core-plugin-api": "workspace:^", |
Spotted by Diamond
Is this helpful? React 👍 or 👎 to let us know.
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub. |
|
This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution! |
2 participants
Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.
Snyk changed the following file(s):
plugins/catalog/package.jsonNote for zero-installs users
If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the
.yarn/cache/directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to runyarnto update the contents of the./yarn/cachedirectory.If you are not using zero-install you can ignore this as your flow should likely be unchanged.
Vulnerabilities that will be fixed with an upgrade:
SNYK-JS-TARFS-10293725
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Improper Link Resolution Before File Access ('Link Following')
Summary by Sourcery
Upgrade the @backstage/core-plugin-api dependency in the catalog plugin to version 0.1.0 to resolve a security vulnerability.
Bug Fixes:
Chores: