[Snyk] Fix for 1 vulnerabilities#4476
Closed
snyk-io[bot] wants to merge 1 commit intomasterfrom
Closed
Conversation
…erabilities The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-TARFS-9535930
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 several Updated class diagram for package.json dependenciesclassDiagram
class PackageJson {
dependencies: Object<string, string>
}
PackageJson --|> BackendCommon
PackageJson --|> CatalogModel
PackageJson --|> PluginCatalogCommon
PackageJson --|> PluginCatalogNode
class BackendCommon {
version: string
-version: string
+version: string
}
note for BackendCommon "Updated from workspace:^ to 0.24.1"
class CatalogModel {
version: string
-version: string
+version: string
}
note for CatalogModel "Updated from workspace:^ to 0.1.1"
class PluginCatalogCommon {
version: string
-version: string
+version: string
}
note for PluginCatalogCommon "Updated from workspace:^ to 0.1.0"
class PluginCatalogNode {
version: string
-version: string
+version: string
}
note for PluginCatalogNode "Updated from workspace:^ to 1.0.0"
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.
![graphite-app[bot]](https://avatars.githubusercontent.com/in/158384?s=60&v=4){kind=small}
Comment on lines
+48
to
+56
| "@backstage/backend-common": "0.24.1", | ||
| "@backstage/backend-plugin-api": "workspace:^", | ||
| "@backstage/backend-tasks": "workspace:^", | ||
| "@backstage/catalog-model": "workspace:^", | ||
| "@backstage/catalog-model": "0.1.1", | ||
| "@backstage/config": "workspace:^", | ||
| "@backstage/errors": "workspace:^", | ||
| "@backstage/integration": "workspace:^", | ||
| "@backstage/plugin-catalog-common": "workspace:^", | ||
| "@backstage/plugin-catalog-node": "workspace:^", | ||
| "@backstage/plugin-catalog-common": "0.1.0", | ||
| "@backstage/plugin-catalog-node": "1.0.0", |
There was a problem hiding this comment.
The version numbers specified in this PR appear inconsistent with typical Backstage versioning patterns. For example, @backstage/catalog-model at version 0.1.1 is significantly lower than current stable releases, which are typically in the range of 1.x.
Additionally, the PR description contains a warning that the yarn.lock file wasn't updated properly, which is critical for dependency resolution in Yarn workspaces.
Before merging, please:
- Verify these versions against the latest compatible Backstage packages
- Ensure the
yarn.lockfile is properly updated - Consider whether pinning specific versions (rather than using
workspace:^) is appropriate for your project structure
These issues could lead to dependency conflicts or broken functionality if not addressed.
Suggested change
| "@backstage/backend-common": "0.24.1", | |
| "@backstage/backend-plugin-api": "workspace:^", | |
| "@backstage/backend-tasks": "workspace:^", | |
| "@backstage/catalog-model": "workspace:^", | |
| "@backstage/catalog-model": "0.1.1", | |
| "@backstage/config": "workspace:^", | |
| "@backstage/errors": "workspace:^", | |
| "@backstage/integration": "workspace:^", | |
| "@backstage/plugin-catalog-common": "workspace:^", | |
| "@backstage/plugin-catalog-node": "workspace:^", | |
| "@backstage/plugin-catalog-common": "0.1.0", | |
| "@backstage/plugin-catalog-node": "1.0.0", | |
| "@backstage/backend-common": "workspace:^", | |
| "@backstage/backend-plugin-api": "workspace:^", | |
| "@backstage/backend-tasks": "workspace:^", | |
| "@backstage/catalog-model": "workspace:^", | |
| "@backstage/config": "workspace:^", | |
| "@backstage/errors": "workspace:^", | |
| "@backstage/integration": "workspace:^", | |
| "@backstage/plugin-catalog-common": "workspace:^", | |
| "@backstage/plugin-catalog-node": "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! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
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-azure/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-TARFS-9535930
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:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.
Summary by Sourcery
Update dependencies to fix a high-severity security vulnerability in the Backstage Azure catalog backend module
Bug Fixes:
Enhancements: