[Snyk] Fix for 1 vulnerabilities#4031
Conversation
…nerabilities The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-OCTOKITREQUESTERROR-8730854
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 Guide by SourceryThis pull request upgrades No diagrams generated as the changes look simple and do not need a visual representation. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
We have skipped reviewing this pull request. Here's why:
- It seems to have been created by a bot (hey, snyk-io[bot]!). We assume it knows what it's doing!
- It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
- We don't review packaging changes - Let us know if you'd like us to change this.
|
Warning Review the following alerts detected in dependencies. According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. 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 checks have failed. 1 issues have been found so far.
⛔ security/snyk check is complete. 1 issues have been found. (View Details) 💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub. |
![graphite-app[bot]](https://avatars.githubusercontent.com/in/158384?s=60&v=4){kind=small}
| "@backstage/catalog-model": "0.1.1", | ||
| "@backstage/config": "workspace:^", | ||
| "@backstage/errors": "workspace:^", | ||
| "@backstage/integration": "workspace:^", | ||
| "@backstage/plugin-catalog-backend": "workspace:^", | ||
| "@backstage/plugin-catalog-common": "workspace:^", | ||
| "@backstage/plugin-catalog-backend": "1.25.0", | ||
| "@backstage/plugin-catalog-common": "0.1.0", |
There was a problem hiding this comment.
The version changes in this PR raise compatibility concerns. Replacing workspace:^ references with fixed versions (0.1.1, 1.25.0, 0.1.0) creates a significant version disparity between packages. This approach:
- May introduce compatibility issues between these packages and other workspace dependencies
- Breaks the monorepo development workflow by forcing specific registry versions instead of using local workspace references
- Could prevent developers from using local changes during development
Consider addressing the vulnerability while maintaining workspace references, possibly by upgrading the affected dependencies across the entire project rather than pinning specific versions in this single module.
| "@backstage/catalog-model": "0.1.1", | |
| "@backstage/config": "workspace:^", | |
| "@backstage/errors": "workspace:^", | |
| "@backstage/integration": "workspace:^", | |
| "@backstage/plugin-catalog-backend": "workspace:^", | |
| "@backstage/plugin-catalog-common": "workspace:^", | |
| "@backstage/plugin-catalog-backend": "1.25.0", | |
| "@backstage/plugin-catalog-common": "0.1.0", | |
| "@backstage/catalog-model": "workspace:^", | |
| "@backstage/config": "workspace:^", | |
| "@backstage/errors": "workspace:^", | |
| "@backstage/integration": "workspace:^", | |
| "@backstage/plugin-catalog-backend": "workspace:^", | |
| "@backstage/plugin-catalog-common": "workspace:^", |
Spotted by Diamond
Is this helpful? React 👍 or 👎 to let us know.
|
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! |
1 participant
Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.
Snyk changed the following file(s):
plugins/catalog-backend-module-github/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-OCTOKITREQUESTERROR-8730854
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
Bug Fixes:
@backstage/catalog-model,@backstage/plugin-catalog-backend, and@backstage/plugin-catalog-common.