[Snyk] Security upgrade @backstage/types from 0.0.0-use.local to 0.1.1#5332
[Snyk] Security upgrade @backstage/types from 0.0.0-use.local to 0.1.1#5332snyk-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/types dependency from a local workspace specifier to explicit version 0.1.1 in packages/config/package.json, addressing a high-severity tar-fs vulnerability (SNYK-JS-TARFS-10293725). Sequence Diagram: Snyk Automated Dependency Upgrade for @backstage/typessequenceDiagram
title "Sequence Diagram: Snyk Automated Dependency Upgrade for @backstage/types"
actor SnykService as "Snyk Service"
participant CodeRepository as "Code Repository"
participant PackageConfig as "packages/config/package.json"
actor Developer
SnykService->>CodeRepository: 1. Scan for vulnerabilities
activate SnykService
activate CodeRepository
CodeRepository-->>SnykService: 2. Vulnerability found in @backstage/types (SNYK-JS-TARFS-10293725)
deactivate CodeRepository
SnykService->>CodeRepository: 3. Create Pull Request to upgrade @backstage/types
activate CodeRepository
SnykService->>PackageConfig: 4. Propose update in PR: @backstage/types "workspace:^" to "0.1.1"
activate PackageConfig
Note right of PackageConfig: Change is applied to this file
deactivate PackageConfig
deactivate SnykService
Developer->>CodeRepository: 5. Review PR
activate Developer
Note over Developer, CodeRepository: Considers yarn.lock manual update (as per Snyk warning)
Developer->>CodeRepository: 6. Merge PR
deactivate Developer
deactivate CodeRepository
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}
| }, | ||
| "dependencies": { | ||
| "@backstage/types": "workspace:^", | ||
| "@backstage/types": "0.1.1", |
There was a problem hiding this comment.
This change replaces the workspace dependency reference workspace:^ with a fixed version 0.1.1, which breaks the monorepo's dependency structure. In a monorepo, workspace references ensure that local versions of packages are used during development rather than versions from the npm registry.
While addressing the security vulnerability is important, changing the dependency format will cause the package to use the external npm version instead of the local workspace version. This can lead to:
- Version inconsistencies across the monorepo
- Difficulty in testing local changes across packages
- Potential build and runtime issues
Consider addressing the security vulnerability while maintaining the workspace reference format. This might involve updating the local package version while keeping the workspace:^ syntax intact.
| "@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. |
|
Warning Review the following alerts detected in dependencies. According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. 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):
packages/config/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: