Conversation
….json to reduce vulnerabilities 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 patches a high-severity TARFS vulnerability by replacing workspace wildcard references with explicit, patched version pins for core Backstage and scaffolder dependencies in the Confluence-to-Markdown plugin’s package.json. Class Diagram: Updated 'dependencies' in scaffolder-backend-module-confluence-to-markdown/package.jsonclassDiagram
class Dependencies_scaffolder_confluence_module {
<<section in package.json>>
"@backstage/backend-common": "version 0.24.1 (was workspace:^)"
"@backstage/config": "version workspace:^"
"@backstage/errors": "version workspace:^"
"@backstage/integration": "version workspace:^"
"@backstage/plugin-scaffolder-backend": "version 1.24.0 (was workspace:^)"
"@backstage/plugin-scaffolder-node": "version 0.4.5 (was workspace:^)"
"@backstage/types": "version workspace:^"
"fs-extra": "version 10.1.0"
"git-url-parse": "version ^13.1.0"
"turndown": "version ^7.1.1"
"turndown-plugin-gfm": "version ^1.0.2"
"uuid": "version ^9.0.0"
"winston": "version ^3.2.1"
"yaml": "version ^2.1.1"
"zod": "version ^3.20.2"
}
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) |
|
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! |
| "@backstage/backend-common": "0.24.1", | ||
| "@backstage/config": "workspace:^", | ||
| "@backstage/errors": "workspace:^", | ||
| "@backstage/integration": "workspace:^", | ||
| "@backstage/plugin-scaffolder-backend": "workspace:^", | ||
| "@backstage/plugin-scaffolder-node": "workspace:^", | ||
| "@backstage/plugin-scaffolder-backend": "1.24.0", | ||
| "@backstage/plugin-scaffolder-node": "0.4.5", |
There was a problem hiding this comment.
This PR changes workspace references (workspace:^) to pinned versions for several Backstage packages, but the warning in the PR description indicates that the yarn.lock file update failed.
Without a properly updated yarn.lock file, this change could cause dependency resolution issues when the project is built, as the pinned versions might not be compatible with other workspace packages that expect different versions.
Before merging, ensure that:
- The yarn.lock file is manually updated to reflect these version changes
- The project builds successfully with the updated dependencies
- All tests pass with the new dependency versions
This is particularly important in a monorepo setup where multiple packages may depend on compatible versions of these core Backstage libraries.
Spotted by Diamond
Is this helpful? React 👍 or 👎 to let us know.
|
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/scaffolder-backend-module-confluence-to-markdown/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: