[Snyk] Security upgrade @backstage/core-plugin-api from 0.0.0-use.local to 0.1.0#5397
Closed
snyk-io[bot] wants to merge 1 commit intomasterfrom
Closed
[Snyk] Security upgrade @backstage/core-plugin-api from 0.0.0-use.local to 0.1.0#5397snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-io[bot] wants to merge 1 commit intomasterfrom
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 GuideThis PR upgrades the @backstage/core-plugin-api dependency in the code-coverage plugin to version 0.1.0 to remediate a high-severity TarFS link-following vulnerability, and flags a manual yarn.lock update required due to automated lockfile failure. Sequence Diagram: Snyk Automated Dependency Upgrade ProcesssequenceDiagram
title "Sequence Diagram: Snyk Automated Dependency Upgrade Process"
actor SnykBot as "Snyk (Bot)"
actor Developer
participant ProjectRepository as "Project Repository"
participant PackageFile as "plugins/code-coverage/package.json"
participant YarnLock as "yarn.lock"
SnykBot->>ProjectRepository: Scans dependencies
SnykBot->>ProjectRepository: Detects vulnerability SNYK-JS-TARFS-10293725 in @backstage/core-plugin-api (v0.0.0-use.local)
SnykBot->>ProjectRepository: Creates Pull Request to upgrade dependency
activate SnykBot
ProjectRepository->>PackageFile: Update "@backstage/core-plugin-api" from "0.0.0-use.local" to "0.1.0"
SnykBot-->>YarnLock: Attempts to update yarn.lock (fails in this case)
SnykBot-->>Developer: Warns: "Failed to update yarn.lock, please update manually before merging"
deactivate SnykBot
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
Author
🎉 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/config": "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 replaces the workspace reference with a fixed version number (0.1.0), which breaks the monorepo's workspace dependency structure. In a monorepo, workspace:^ ensures the package uses the local version from the workspace rather than downloading from npm.
Using a fixed version will:
- Force fetching from npm instead of using local code
- Create inconsistencies with other dependencies
- Potentially break builds when local API changes aren't reflected
The dependency should remain as workspace:^ to maintain proper monorepo functionality while still addressing the security vulnerability through updates to the local package.
Suggested change
| "@backstage/core-plugin-api": "0.1.0", | |
| "@backstage/core-plugin-api": "workspace:^", |
Spotted by Diamond
Is this helpful? React 👍 or 👎 to let us know.
|
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! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.
Snyk changed the following file(s):
plugins/code-coverage/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
Bug Fixes: