Skip to content

[Snyk] Security upgrade @backstage/plugin-search-common from 0.0.0-use.local to 0.3.1 #9902

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] Security upgrade @backstage/plugin-search-common from 0.0.0-use.local to 0.3.1 #9902

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/catalog-common/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@
"dependencies": {
"@backstage/catalog-model": "workspace:^",
"@backstage/plugin-permission-common": "workspace:^",
"@backstage/plugin-search-common": "workspace:^"
"@backstage/plugin-search-common": "0.3.1"
Copy link

@augmentcode augmentcode bot Jan 10, 2026

Choose a reason for hiding this comment

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

@backstage/plugin-search-common is also a local workspace package in this repo (plugins/search-common, currently v1.2.5); pinning 0.3.1 will force Yarn to fetch an older external copy instead of using the workspace package.
This can introduce duplicate/mismatched Backstage packages and break builds/runtime expectations in the monorepo.

Fix This in Augment

🤖 Was this useful? React with 👍 or 👎

Copy link

@augmentcode augmentcode bot Jan 10, 2026

Choose a reason for hiding this comment

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

Snyk notes the lockfile update failed; since yarn.lock isn’t updated in this PR, CI may still resolve the previous dependency graph (or fail due to an out-of-sync lockfile).
Before merging, make sure the lockfile reflects the intended resolution for this dependency change (especially if using zero-installs).

Fix This in Augment

🤖 Was this useful? React with 👍 or 👎

},
"devDependencies": {
"@backstage/cli": "workspace:^"
Expand Down
Loading