[Snyk] Security upgrade @backstage/types from 0.0.0-use.local to 0.1.1#5296
[Snyk] Security upgrade @backstage/types from 0.0.0-use.local to 0.1.1#5296snyk-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 bumps the @backstage/types dependency in plugins/search-react from a local workspace reference to version 0.1.1 to address a high-severity TARFS vulnerability, and requires a manual yarn.lock update before merging. Sequence Diagram: Snyk Automated Dependency Upgrade ProcesssequenceDiagram
actor SnykBot as "Snyk Bot"
participant CodeRepository as "Code Repository"
actor Developer
SnykBot->>CodeRepository: Scans dependencies for vulnerabilities
SnykBot->>CodeRepository: Detects vulnerability (SNYK-JS-TARFS-10293725) in @backstage/types
SnykBot->>CodeRepository: Creates Pull Request to upgrade @backstage/types from 'workspace:^' to '0.1.1' in 'plugins/search-react/package.json'
CodeRepository-->>Developer: Notifies of new Pull Request
Developer->>CodeRepository: Reviews Pull Request
Developer->>CodeRepository: Manually updates yarn.lock (as prompted in PR)
Developer->>CodeRepository: Merges Pull Request
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
| "@backstage/plugin-search-common": "workspace:^", | ||
| "@backstage/theme": "workspace:^", | ||
| "@backstage/types": "workspace:^", | ||
| "@backstage/types": "0.1.1", |
There was a problem hiding this comment.
Replacing workspace:^ with a fixed version (0.1.1) in a monorepo context can lead to dependency resolution issues and break the workspace linking system.
In a monorepo setup, the workspace:^ syntax ensures packages reference each other correctly within the workspace. Instead of changing this reference pattern:
- Update the actual
@backstage/typespackage within your workspace to a secure version - Keep the
workspace:^reference in this file - Update the yarn.lock file as noted in the PR description
This approach maintains proper workspace relationships while addressing the security vulnerability.
| "@backstage/types": "0.1.1", | |
| "@backstage/types": "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! |
Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.
Snyk changed the following file(s):
plugins/search-react/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: