forked from SDA-SE/backstage
-
Notifications
You must be signed in to change notification settings - Fork 1
[Snyk] Fix for 4 vulnerabilities #11549
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
Open
q1blue
wants to merge
1
commit into
master
Choose a base branch
from
snyk-fix-2478bfe3c880db2d8a014b6832c816ac
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+4
−4
Open
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 change introduces significant downgrades for several core
@backstagepackages by replacingworkspace:^with outdated, pinned versions. This poses a critical risk of breaking the application due to version mismatches and API incompatibilities.The following packages are being downgraded:
@backstage/config: from1.0.8(in workspace) to0.1.1@backstage/core-components: from0.13.4-next.0(in workspace) to0.8.6@backstage/core-plugin-api: from1.5.3(in workspace) to0.1.0@backstage/theme: from0.4.1(in workspace) to0.1.1Using
workspace:^is standard practice in this monorepo to ensure internal packages stay in sync. Pinning to old versions breaks this mechanism.The vulnerabilities this PR aims to fix likely originate from transitive
devDependencies(e.g., via@backstage/cli), not these direct dependencies. A better approach would be to target the vulnerable packages directly, for example by usingresolutionsin the rootpackage.jsonor updating the packages that introduce the vulnerabilities.I recommend reverting this change to avoid breaking the project.