[Snyk] Security upgrade @backstage/plugin-scaffolder-backend from 0.0.0-use.local to 0.1.1#5239
[Snyk] Security upgrade @backstage/plugin-scaffolder-backend from 0.0.0-use.local to 0.1.1#5239snyk-io[bot] wants to merge 1 commit intomasterfrom
Conversation
…ulnerabilities The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-MULTER-10185673 - https://snyk.io/vuln/SNYK-JS-MULTER-10185675
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
|
No applications have been configured for previews targeting branch: master. To do so go to restack console and configure your applications for previews. |
Reviewer's GuidePins the @backstage/plugin-scaffolder-backend dependency to version 0.1.1 in package.json to remediate two high-severity Multer vulnerabilities; reviewers must manually update the yarn.lock before merging. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
⛔ Snyk checks have failed. 2 issues have been found so far.
⛔ security/snyk check is complete. 2 issues have been found. (View Details) 💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
![graphite-app[bot]](https://avatars.githubusercontent.com/in/158384?s=60&v=4){kind=small}
| "@backstage/errors": "workspace:^", | ||
| "@backstage/integration": "workspace:^", | ||
| "@backstage/plugin-scaffolder-backend": "workspace:^", | ||
| "@backstage/plugin-scaffolder-backend": "0.1.1", |
There was a problem hiding this comment.
Changing from a workspace reference (workspace:^) to a pinned version (0.1.1) breaks the local package linking that's essential in a monorepo setup. This will likely cause compatibility issues with other local packages that expect to use the workspace version.
The PR description confirms that the yarn.lock update failed, which is a clear indicator of dependency resolution problems. Before merging:
- Run
yarnto properly update all dependencies - Verify the yarn.lock file is correctly updated
- Consider whether this security fix should be applied through a different approach that maintains workspace references
If the goal is to address the multer vulnerabilities, it might be better to update the dependency in the main package rather than changing the reference pattern.
| "@backstage/plugin-scaffolder-backend": "0.1.1", | |
| + "@backstage/plugin-scaffolder-backend": "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 2 vulnerabilities in the yarn dependencies of this project.
Snyk changed the following file(s):
plugins/scaffolder-backend-module-rails/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-MULTER-10185673
SNYK-JS-MULTER-10185675
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:
🦉 Uncaught Exception
🦉 Missing Release of Memory after Effective Lifetime
Summary by Sourcery
Mitigate security vulnerabilities in Multer by updating the @backstage/plugin-scaffolder-backend dependency to version 0.1.1 in the Rails scaffolder backend module.
Bug Fixes:
Enhancements: