Skip to content

[Snyk] Fix for 3 vulnerabilities #9908

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

Open
q1blue wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Snyk] Fix for 3 vulnerabilities #9908

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
6 changes: 3 additions & 3 deletions plugins/scaffolder-backend-module-confluence-to-markdown/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,12 +24,12 @@
"help": "backstage-cli help"
},
"dependencies": {
"@backstage/backend-common": "workspace:^",
"@backstage/backend-common": "0.24.1",
Copy link

@augmentcode augmentcode bot Jan 13, 2026

Choose a reason for hiding this comment

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

Pinning @backstage/* deps here to 0.24.1/1.24.0/0.2.0 won’t match the in-repo workspace package versions (e.g. @backstage/plugin-scaffolder-backend is 1.15.2-next.0), so Yarn will likely pull published packages from the registry instead of using the local workspaces. That can lead to duplicate @backstage/* installs and runtime/type mismatches (also applies to the other pinned @backstage/* lines in this file).

Fix This in Augment

🤖 Was this useful? React with 👍 or 👎

"@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",
Copy link

@augmentcode augmentcode bot Jan 13, 2026

Choose a reason for hiding this comment

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

The PR description notes yarn.lock wasn’t updated; if it stays unchanged, installs/CI may not consistently pick up the intended new resolutions. This can also make it harder to verify that the vulnerability fixes are actually in effect for the module.

Fix This in Augment

🤖 Was this useful? React with 👍 or 👎

"@backstage/plugin-scaffolder-node": "0.2.0",
"@backstage/types": "workspace:^",
"fs-extra": "10.1.0",
"git-url-parse": "^13.1.0",
Expand Down
Loading