[Snyk] Fix for 4 vulnerabilities

[snyk-io]

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

Snyk changed the following file(s):

• plugins/github-actions/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
	Regular Expression Denial of Service (ReDoS) SNYK-JS-DIFF-14917201	590
	UNIX Symbolic Link (Symlink) Following SNYK-JS-BACKSTAGEBACKENDPLUGINAPI-15054291	550
	Prototype Pollution SNYK-JS-LODASH-15053838	545
	Prototype Pollution SNYK-JS-LODASHES-15053836	545

---

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:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Prototype Pollution

---

EntelligenceAI PR Summary

This PR updates dependency version specifications in the github-actions plugin, replacing workspace protocol references with explicit semantic versions for Backstage packages.

• Changed @backstage/core-components from workspace:^ to 0.1.0
• Changed @backstage/integration from workspace:^ to 0.1.0
• Changed @backstage/integration-react from workspace:^ to 0.1.1
• Changed @backstage/plugin-catalog-react from workspace:^ to 0.0.1
• Transitions from monorepo workspace dependencies to published package versions

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[snyk-io]

⛔ Snyk checks have failed. 1 issues have been found so far.

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

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

[entelligence-ai-pr-reviews]

Walkthrough

This PR transitions the github-actions plugin from using workspace protocol dependencies to explicit semantic versioning for Backstage packages. Four core Backstage dependencies are updated with pinned versions: @backstage/core-components and @backstage/integration are set to version 0.1.0, @backstage/integration-react to 0.1.1, and @backstage/plugin-catalog-react to 0.0.1. This change represents a shift from monorepo workspace-based dependency resolution to published package versions, which will affect how dependencies are resolved during installation and may indicate preparation for independent package distribution or release.

Changes

File(s)	Summary
plugins/github-actions/package.json	Updated four Backstage package dependencies from workspace protocol (workspace:^) to explicit semantic versions: @backstage/core-components@0.1.0, @backstage/integration@0.1.0, @backstage/integration-react@0.1.1, and @backstage/plugin-catalog-react@0.0.1.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant PM as Package Manager
    participant GHA as github-actions plugin
    participant CC as @backstage/core-components
    participant INT as @backstage/integration
    participant INTR as @backstage/integration-react
    participant PCR as @backstage/plugin-catalog-react
    
    Note over PM,PCR: Dependency Resolution Change
    
    PM->>GHA: Install dependencies
    
    Note over GHA: Before: workspace:^ references
    GHA-->>PM: Resolve from local workspace
    
    Note over GHA,PCR: After: Fixed version references
    GHA->>CC: Require v0.1.0
    GHA->>INT: Require v0.1.0
    GHA->>INTR: Require v0.1.1
    GHA->>PCR: Require v0.0.1
    
    PM->>CC: Fetch v0.1.0 from registry
    PM->>INT: Fetch v0.1.0 from registry
    PM->>INTR: Fetch v0.1.1 from registry
    PM->>PCR: Fetch v0.0.1 from registry
    
    Note over PM,PCR: Dependencies now pinned to specific versions

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.

[github-actions]

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!