[Snyk] Fix for 1 vulnerabilities#10884
Conversation
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-TAR-15032660
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub. |
|
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.
|
|
| Status | Scanner |  Critical |
 High |
 Medium |
 Low |
Total (0) |
|---|---|---|---|---|---|---|
| Open Source Security | 0 | 0 | 0 | 0 | See details |
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.
![entelligence-ai-pr-reviews[bot]](https://avatars.githubusercontent.com/in/932812?s=60&v=4){kind=small}
There was a problem hiding this comment.
Walkthrough
This PR updates dependency versions in the backend-common package, focusing on both internal Backstage packages and external dependencies. The changes transition three Backstage packages from workspace protocol to fixed versions (backend-app-api, backend-plugin-api, and integration-aws-node), indicating a shift toward stable release versions. Additionally, two external dependencies receive significant upgrades: @kubernetes/client-node jumps from 0.18.1 to 0.21.0, and tar undergoes a major version upgrade from 6.1.12 to 7.5.4. These updates likely prepare the package for publication and may introduce new features or breaking changes, particularly in the Kubernetes client and tar library functionality.
Changes
| File(s) | Summary |
|---|---|
packages/backend-common/package.json |
Updated Backstage internal dependencies from workspace protocol to fixed versions: @backstage/backend-app-api (0.5.0), @backstage/backend-plugin-api (0.6.19), @backstage/integration-aws-node (0.1.0). Upgraded external dependencies: @kubernetes/client-node from 0.18.1 to 0.21.0 and tar from 6.1.12 to 7.5.4. |
Sequence Diagram
This diagram shows the interactions between components:
sequenceDiagram
participant Dev as Developer
participant Package as backend-common package.json
participant Deps as Dependencies
Dev->>Package: Update dependency versions
Note over Package: Backstage packages:<br/>- backend-app-api: workspace → 0.5.0<br/>- backend-plugin-api: workspace → 0.6.19<br/>- integration-aws-node: workspace → 0.1.0
Note over Package: External packages:<br/>- @kubernetes/client-node: 0.18.1 → 0.21.0<br/>- tar: 6.1.12 → 7.5.4
Package->>Deps: Lock to specific versions
Deps-->>Package: Dependencies resolved
Package-->>Dev: Package updated
Install the extension
Note for Windsurf
Please change the default marketplace provider to the following in the windsurf settings:Marketplace Extension Gallery Service URL: https://marketplace.visualstudio.com/_apis/public/gallery
Marketplace Gallery Item URL: https://marketplace.visualstudio.com/items
Entelligence.ai can learn from your feedback. Simply add 👍 / 👎 emojis to teach it your preferences. More shortcuts below
Emoji Descriptions:
⚠️ Potential Issue - May require further investigation.- 🔒 Security Vulnerability - Fix to ensure system safety.
- 💻 Code Improvement - Suggestions to enhance code quality.
- 🔨 Refactor Suggestion - Recommendations for restructuring code.
- ℹ️ Others - General comments and information.
Interact with the Bot:
- Send a message or request using the format:
@entelligenceai + *your message*
Example: @entelligenceai Can you suggest improvements for this code?
- Help the Bot learn by providing feedback on its responses.
@entelligenceai + *feedback*
Example: @entelligenceai Do not comment on `save_auth` function !
Also you can trigger various commands with the bot by doing
@entelligenceai command
The current supported commands are
config- shows the current configretrigger_review- retriggers the review
More commands to be added soon.
| "@backstage/backend-app-api": "0.5.0", | ||
| "@backstage/backend-dev-utils": "workspace:^", | ||
| "@backstage/backend-plugin-api": "workspace:^", | ||
| "@backstage/backend-plugin-api": "0.6.19", | ||
| "@backstage/cli-common": "workspace:^", | ||
| "@backstage/config": "workspace:^", | ||
| "@backstage/config-loader": "workspace:^", | ||
| "@backstage/errors": "workspace:^", | ||
| "@backstage/integration": "workspace:^", | ||
| "@backstage/integration-aws-node": "workspace:^", | ||
| "@backstage/integration-aws-node": "0.1.0", | ||
| "@backstage/types": "workspace:^", |
There was a problem hiding this comment.
Correctness: Replacing workspace:^ with fixed versions for internal packages (@backstage/backend-app-api, etc.) breaks monorepo linking and forces registry fetches. Revert to workspace:^ to ensure local packages are resolved correctly.
🤖 AI Agent Prompt for Cursor/Windsurf
📋 Copy this prompt to your AI coding assistant (Cursor, Windsurf, etc.) to get help fixing this issue
File: packages/backend-common/package.json
Lines: 53-62
Problem: The diff replaces workspace protocol dependencies with fixed versions for internal Backstage packages (@backstage/backend-app-api, @backstage/backend-plugin-api, @backstage/integration-aws-node) and upgrades @kubernetes/client-node from 0.18.1 to 0.21.0. This breaks monorepo workspace linking and may introduce breaking changes.
Fix Instructions:
1. Revert @backstage/* packages back to 'workspace:^' to maintain monorepo workspace linking
2. If upgrading @kubernetes/client-node is necessary, verify all usages in the codebase are compatible with v0.21.0 API changes (check migration guides between 0.18.1 → 0.19.x → 0.20.x → 0.21.0)
3. Run integration tests to ensure no breaking changes from the Kubernetes client upgrade
4. If fixed versions are intentionally required for publishing, this should be handled by the build/release pipeline, not in source package.json
✨ Committable Code Suggestion
💡 This is a one-click fix! Click "Commit suggestion" to apply this change directly to your branch.
| "@backstage/backend-app-api": "0.5.0", | |
| "@backstage/backend-dev-utils": "workspace:^", | |
| "@backstage/backend-plugin-api": "workspace:^", | |
| "@backstage/backend-plugin-api": "0.6.19", | |
| "@backstage/cli-common": "workspace:^", | |
| "@backstage/config": "workspace:^", | |
| "@backstage/config-loader": "workspace:^", | |
| "@backstage/errors": "workspace:^", | |
| "@backstage/integration": "workspace:^", | |
| "@backstage/integration-aws-node": "workspace:^", | |
| "@backstage/integration-aws-node": "0.1.0", | |
| "@backstage/types": "workspace:^", | |
| "@aws-sdk/abort-controller": "^3.347.0", | |
| "@aws-sdk/client-s3": "^3.350.0", | |
| "@aws-sdk/credential-providers": "^3.350.0", | |
| "@aws-sdk/types": "^3.347.0", | |
| "@backstage/backend-app-api": "workspace:^", | |
| "@backstage/backend-dev-utils": "workspace:^", | |
| "@backstage/backend-plugin-api": "workspace:^", | |
| "@backstage/cli-common": "workspace:^", | |
| "@backstage/config": "workspace:^", | |
| "@backstage/config-loader": "workspace:^", | |
| "@backstage/errors": "workspace:^", | |
| "@backstage/integration": "workspace:^", | |
| "@backstage/integration-aws-node": "workspace:^", | |
| "@backstage/types": "workspace:^", | |
| "@google-cloud/storage": "^6.0.0", | |
| "@keyv/memcache": "^1.3.5", | |
| "@keyv/redis": "^2.5.3", | |
| "@kubernetes/client-node": "0.18.1", | |
| "@manypkg/get-packages": "^1.1.3", | |
| "@octokit/rest": "^19.0.3", | |
| "@types/cors": "^2.8.6", |
|
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):
packages/backend-common/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-TAR-15032660
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:
🦉 Directory Traversal
EntelligenceAI PR Summary
This PR updates dependency versions in backend-common package, transitioning internal Backstage packages to fixed versions and upgrading external dependencies.