Skip to content

[Snyk] Security upgrade @backstage/errors from 0.0.0-use.local to 0.1.1#11766

Closed
snyk-io[bot] wants to merge 2 commits intomasterfrom
snyk-fix-88f76ce4683a06d3c5af2ee6d2bc728d
Closed

[Snyk] Security upgrade @backstage/errors from 0.0.0-use.local to 0.1.1#11766
snyk-io[bot] wants to merge 2 commits intomasterfrom
snyk-fix-88f76ce4683a06d3c5af2ee6d2bc728d

Conversation

@snyk-io
Copy link
Copy Markdown

@snyk-io snyk-io Bot commented Feb 6, 2026

snyk-top-banner

Snyk has created this PR to fix 2 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

  • packages/e2e-test/package.json

Note 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 run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠️ Warning
Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
low severity Server-side Request Forgery (SSRF)
SNYK-JS-WEBPACK-15235959
  380  
low severity Server-side Request Forgery (SSRF)
SNYK-JS-WEBPACK-15235969
  380  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

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:

🦉 Server-side Request Forgery (SSRF)


EntelligenceAI PR Summary

This PR pins the @backstage/errors dependency in the e2e-test package to a specific external version instead of using the workspace version.

  • Modified packages/e2e-test/package.json to use version 0.1.1 of @backstage/errors
  • Replaced workspace dependency resolution (workspace:^) with fixed external version
  • Ensures e2e tests run against a stable, published version of the errors package

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Feb 6, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@entelligence-ai-pr-reviews
Copy link
Copy Markdown

Walkthrough

This PR modifies the dependency management strategy for the e2e-test package by switching from a workspace-based dependency resolution to a pinned external version. The @backstage/errors package dependency is changed from workspace:^ to a fixed version 0.1.1, effectively decoupling the e2e-test package from the local workspace version of the errors package. This change likely aims to ensure consistent testing behavior by using a stable, published version rather than the potentially evolving workspace version, or may serve as a temporary solution to address workspace dependency resolution issues.

Changes

File(s) Summary
packages/e2e-test/package.json Changed @backstage/errors dependency from workspace reference (workspace:^) to fixed external version (0.1.1).

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PM as Package Manager
    participant Registry as NPM Registry
    participant E2E as e2e-test Package
    
    Note over Dev,E2E: Dependency Resolution Change
    
    Dev->>PM: Update package.json<br/>(@backstage/errors: workspace:^ → 0.1.1)
    
    alt Build Process (Before)
        PM->>E2E: Resolve workspace:^ dependency
        E2E->>PM: Link to local workspace package
    else Build Process (After)
        PM->>Registry: Request @backstage/errors@0.1.1
        Registry-->>PM: Return published package
        PM->>E2E: Install version 0.1.1
    end
    
    Note over PM,E2E: e2e-test now uses published<br/>version instead of workspace link
Loading

▶️AI Code Reviews for VS Code, Cursor, Windsurf
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

  1. config - shows the current config
  2. retrigger_review - retriggers the review

More commands to be added soon.

@snyk-io
Copy link
Copy Markdown
Author

snyk-io Bot commented Feb 6, 2026

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Mar 6, 2026

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!

@github-actions github-actions Bot added the stale label Mar 6, 2026
@github-actions github-actions Bot closed this Mar 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant