forked from SDA-SE/backstage
-
Notifications
You must be signed in to change notification settings - Fork 1
[Snyk] Fix for 3 vulnerabilities #12088
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.
These dependency updates are incorrect and will likely break the application for several reasons:
Improper Pinning of Workspace Dependencies: The change from
workspace:^to pinned versions is an anti-pattern in a Yarn workspace monorepo. It bypasses the intended local package linking, which can lead to multiple versions of the same package and hard-to-diagnose bugs. The correct way to update these is to update the package versions at their source within the monorepo.Major Package Downgrades: Some of the pinned versions are severe downgrades from the versions available in the workspace:
@backstage/catalog-clientis downgraded from version1.4.3to0.2.0.@backstage/catalog-modelis downgraded from version1.4.1to0.1.1.These are major version downgrades that are almost certain to introduce breaking changes and cause application failures.
Missing
yarn.lockUpdate: The PR description notes that theyarn.lockfile has not been updated. Any change to dependencies inpackage.jsonmust be accompanied by a corresponding update to the lock file to ensure deterministic and correct installs across all environments.Given these critical issues, these changes should be rejected.