-
Notifications
You must be signed in to change notification settings - Fork 1
[Snyk] Security upgrade @backstage/plugin-scaffolder-backend from 0.0.0-use.local to 1.15.0 #6649
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
base: master
Are you sure you want to change the base?
Conversation
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-OCTOKIT-6129525 - https://snyk.io/vuln/SNYK-JS-OCTOKITWEBHOOKS-6129527 - https://snyk.io/vuln/SNYK-JS-BACKSTAGEPLUGINSCAFFOLDERBACKEND-5730767
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
Reviewer's GuideUpgrades @backstage/plugin-scaffolder-backend from a local workspace reference to version 1.15.0 in package.json to address three high-severity security vulnerabilities (Octokit exceptional handling and arbitrary code injection), and flags the need for a manual yarn.lock update to support zero-installs workflows. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
⛔ Snyk checks have failed. 84 issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
|
No dependency changes detected. Learn more about Socket for GitHub. 👍 No dependency changes detected in pull request |
|
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 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 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! |
Entelligence AI Vulnerability ScannerStatus: No security vulnerabilities found Your code passed our comprehensive security analysis. |
WalkthroughThis pull request modifies the dependency management strategy for the Backstage scaffolder backend plugin in the backend-next package. The change transitions from using a workspace protocol reference (which points to the local monorepo version) to a pinned version (1.15.0) from the npm registry. This modification ensures that the backend-next package uses a specific, stable version of the scaffolder backend plugin rather than the workspace's current development version. This approach can provide version stability, resolve workspace-related dependency issues, or prepare the package for deployment scenarios where workspace dependencies are not available. Changes
Sequence DiagramThis diagram shows the interactions between components: sequenceDiagram
participant Dev as Developer
participant PM as Package Manager
participant WS as Workspace Packages
participant NPM as NPM Registry
participant App as Backend-Next App
Note over Dev,App: Dependency Resolution Change
Dev->>PM: Update package.json
Note right of Dev: Change scaffolder-backend<br/>from workspace:^ to 1.15.0
alt Before Change (workspace:^)
PM->>WS: Resolve @backstage/plugin-scaffolder-backend
WS-->>PM: Return local workspace version
PM->>App: Install local package
else After Change (1.15.0)
PM->>NPM: Fetch @backstage/plugin-scaffolder-backend@1.15.0
NPM-->>PM: Return published package
PM->>App: Install npm package version 1.15.0
end
Note over App: Backend-Next now uses<br/>pinned scaffolder-backend version
Note for WindsurfPlease 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 belowEmoji Descriptions:
Interact with the Bot:
Also you can trigger various commands with the bot by doing The current supported commands are
More commands to be added soon. |
|
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! |
WalkthroughThis pull request modifies the dependency management strategy for the Backstage scaffolder backend plugin in the backend-next package. The change transitions from using a workspace protocol reference (which points to the local monorepo version) to a pinned version (1.15.0) from the npm registry. This modification ensures that the backend-next package uses a specific, stable version of the scaffolder backend plugin rather than the workspace's current development version. This approach can provide version stability, resolve workspace-related dependency issues, or prepare the package for deployment scenarios where workspace dependencies are not available. Changes
Sequence DiagramThis diagram shows the interactions between components: sequenceDiagram
participant Dev as Developer
participant PM as Package Manager
participant WS as Workspace
participant NPM as NPM Registry
participant Backend as backend-next Package
Dev->>PM: Install dependencies
Note over Dev,PM: package.json specifies dependencies
alt Before Change (workspace:^)
PM->>WS: Resolve @backstage/plugin-scaffolder-backend
WS->>PM: Return local workspace version
PM->>Backend: Link local scaffolder-backend
Note over Backend: Uses local development version
else After Change (1.15.0)
PM->>NPM: Fetch @backstage/plugin-scaffolder-backend@1.15.0
NPM->>PM: Return version 1.15.0
PM->>Backend: Install pinned version 1.15.0
Note over Backend: Uses specific published version
end
PM->>Dev: Dependencies installed
Note over Dev,Backend: backend-next now uses<br/>scaffolder-backend v1.15.0<br/>from NPM registry
Note for WindsurfPlease 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 belowEmoji Descriptions:
Interact with the Bot:
Also you can trigger various commands with the bot by doing The current supported commands are
More commands to be added soon. |
EntelligenceAI PR Summary
This PR locks the scaffolder backend plugin dependency to a specific version instead of using the workspace reference.
@backstage/plugin-scaffolder-backendfromworkspace:^to1.15.0packages/backend-next/package.json