[Snyk] Security upgrade @backstage/types from 0.0.0-use.local to 0.1.1#5281
[Snyk] Security upgrade @backstage/types from 0.0.0-use.local to 0.1.1#5281snyk-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 remediates a high-severity vulnerability by explicitly upgrading the @backstage/types dependency in the errors package to version 0.1.1, and flags that the yarn.lock file must be updated manually before merging. Class Diagram: Update to @backstage/types dependency in errors packageclassDiagram
class errors_package_dependencies {
<<JSON Object: dependencies>>
sourceFile: "packages/errors/package.json"
- "@backstage/types": "workspace:^"
+ "@backstage/types": "0.1.1"
}
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
![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 from workspace:^ to a fixed version 0.1.1 breaks the monorepo's workspace dependency resolution. In a monorepo, workspace:^ ensures that the local version of @backstage/types is used during development, maintaining consistency across packages.
Replacing it with a fixed version will:
- Pull
@backstage/typesfrom the npm registry instead of using the local version - Potentially create version conflicts with other packages using the workspace version
- Complicate development workflows as changes to the local
typespackage won't be reflected
While addressing the security vulnerability is important, consider an alternative approach that maintains the workspace structure, such as updating the vulnerable dependency within the types package itself.
| "@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/errors/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: