Skip to content

[Snyk] Security upgrade @backstage/plugin-scaffolder-backend from 0.0.0-use.local to 0.1.1 #5239

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
snyk-io wants to merge 1 commit into from
Closed

[Snyk] Security upgrade @backstage/plugin-scaffolder-backend from 0.0.0-use.local to 0.1.1 #5239

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion plugins/scaffolder-backend-module-rails/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@
"@backstage/config": "workspace:^",
"@backstage/errors": "workspace:^",
"@backstage/integration": "workspace:^",
"@backstage/plugin-scaffolder-backend": "workspace:^",
"@backstage/plugin-scaffolder-backend": "0.1.1",
Copy link
Copy Markdown

@graphite-app graphite-app Bot May 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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:

  1. Run yarn to properly update all dependencies
  2. Verify the yarn.lock file is correctly updated
  3. 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.

Suggested change
"@backstage/plugin-scaffolder-backend": "0.1.1",
+ "@backstage/plugin-scaffolder-backend": "workspace:^",

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.

"@backstage/plugin-scaffolder-node": "workspace:^",
"@backstage/types": "workspace:^",
"command-exists": "^1.2.9",
Expand Down
Loading