forked from SDA-SE/backstage
-
Notifications
You must be signed in to change notification settings - Fork 1
[Snyk] Fix for 3 vulnerabilities #12003
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.
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
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This automated dependency update has introduced several potentially critical issues:
Change in Dependency Strategy: The change from
workspace:^to fixed versions for@backstagepackages (e.g.,@backstage/backend-common,@backstage/plugin-search-backend-module-explore,@backstage/plugin-search-common) alters how dependencies are resolved in this monorepo. Instead of using the local packages from the workspace, they will be fetched from the npm registry. This is a significant change and may not be the intended way to resolve vulnerabilities in a monorepo setup. It's often preferable to update the source of the workspace packages themselves.Major Version Downgrade: The dependency
@backstage/plugin-search-commonis being changed to version0.3.1. Based on the providedplugins/search-common/package.json, the workspace version is1.2.5. This is a major downgrade and is very likely to introduce breaking changes or compilation errors.Missing
yarn.lockupdate: As noted in the pull request description,yarn.lockhas not been updated. This is a critical omission. The lock file must be updated to ensure that the dependency changes are applied correctly and consistently.Given these issues, this PR should be carefully reviewed and likely modified before merging. It's recommended to investigate the vulnerabilities and apply fixes by updating the workspace packages, and then regenerate the
yarn.lockfile.