[Snyk] Fix for 1 vulnerabilities#5074
Conversation
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-BABELRUNTIME-10044504
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
|
No applications have been configured for previews targeting branch: master. To do so go to restack console and configure your applications for previews. |
Reviewer's GuideThis pull request, automatically generated by Snyk, updates specific versions for File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
| "@backstage/config": "0.1.1", | ||
| "@backstage/core-components": "0.1.0", | ||
| "@backstage/core-plugin-api": "workspace:^", | ||
| "@backstage/theme": "workspace:^", | ||
| "@backstage/theme": "0.1.1", |
There was a problem hiding this comment.
This change creates inconsistency in dependency management by converting some Backstage dependencies to fixed versions (@backstage/config, @backstage/core-components, @backstage/theme) while leaving @backstage/core-plugin-api as a workspace reference. This mixed approach may lead to version compatibility issues between these tightly coupled packages.
Additionally, the PR description contains a warning that the yarn.lock file was not updated successfully. This needs to be resolved before merging to ensure proper dependency resolution.
Consider either:
- Converting all Backstage dependencies to fixed versions consistently
- Keeping all as workspace references
- Ensuring the
yarn.lockfile is properly updated to reflect these changes
| "@backstage/config": "0.1.1", | |
| "@backstage/core-components": "0.1.0", | |
| "@backstage/core-plugin-api": "workspace:^", | |
| "@backstage/theme": "workspace:^", | |
| "@backstage/theme": "0.1.1", | |
| + "@backstage/config": "workspace:^", | |
| + "@backstage/core-components": "workspace:^", | |
| "@backstage/core-plugin-api": "workspace:^", | |
| + "@backstage/theme": "workspace:^", | |
Spotted by Diamond
Is this helpful? React 👍 or 👎 to let us know.
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub. |
|
This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution! |
Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.
Snyk changed the following file(s):
plugins/gitops-profiles/package.jsonNote for zero-installs users
If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the
.yarn/cache/directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to runyarnto update the contents of the./yarn/cachedirectory.If you are not using zero-install you can ignore this as your flow should likely be unchanged.
Vulnerabilities that will be fixed with an upgrade:
SNYK-JS-BABELRUNTIME-10044504
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Regular Expression Denial of Service (ReDoS)
Summary by Sourcery
Update package dependencies to fix a security vulnerability in the Babel runtime
Bug Fixes:
Enhancements: