chore(deps): update dependency isolated-vm to v4.7.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
isolated-vm	4.5.0 → 4.7.2

---

Release Notes

laverdet/isolated-vm (isolated-vm)

v4.7.2

Compare Source

v4.6.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[snyk-io]

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

✅ security/snyk check is complete. No issues have been found. (View Details)

[entelligence-ai-pr-reviews]

🔒 Entelligence AI Vulnerability Scanner

✅ No security vulnerabilities found!

Your code passed our comprehensive security analysis.

---

[entelligence-ai-pr-reviews]

Walkthrough

This PR pins specific versions of Backstage dependencies for the gitops-profiles plugin instead of using workspace references. The update fixes the plugin to use exact versions of @backstage/config (0.1.1), @backstage/core-components (0.1.0), @backstage/core-plugin-api (0.1.0), and @backstage/theme (0.1.1). The yarn.lock file has been updated to include all necessary transitive dependencies for these pinned versions. This change appears to be aimed at ensuring compatibility with a specific version of the Backstage framework rather than automatically using the latest workspace versions.

Changes

File(s)	Summary
yarn.lock	Updated dependency tree to pin specific versions of Backstage dependencies (@backstage/config@0.1.1, @backstage/core-components@0.1.0, @backstage/core-plugin-api@0.1.0, @backstage/theme@0.1.1) and their transitive dependencies for the gitops-profiles plugin.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    title Backstage GitOps Profiles Plugin Interaction Flow
    
    actor User
    participant App as "Backstage App"
    participant GitOpsProfilesPlugin as "GitOps Profiles Plugin"
    participant CoreComponents as "Core Components v0.1.0"
    participant CorePluginAPI as "Core Plugin API v0.1.0"
    participant Config as "Config v0.1.1"
    participant Theme as "Theme v0.1.1"
    participant ExternalAPI as "External GitOps API"
    
    User->>App: Navigate to GitOps profiles page
    App->>GitOpsProfilesPlugin: Load plugin
    
    activate GitOpsProfilesPlugin
    
    GitOpsProfilesPlugin->>CorePluginAPI: Register plugin
    CorePluginAPI-->>GitOpsProfilesPlugin: Plugin registered
    
    GitOpsProfilesPlugin->>Config: Load configuration
    Config-->>GitOpsProfilesPlugin: Return configuration
    
    GitOpsProfilesPlugin->>Theme: Apply theme
    Theme-->>GitOpsProfilesPlugin: Theme applied
    
    GitOpsProfilesPlugin->>CoreComponents: Render UI components
    
    activate CoreComponents
    CoreComponents->>CoreComponents: Create Material UI components
    CoreComponents-->>GitOpsProfilesPlugin: UI components rendered
    deactivate CoreComponents
    
    User->>GitOpsProfilesPlugin: Select GitOps profile
    
    GitOpsProfilesPlugin->>ExternalAPI: Request profile deployment
    ExternalAPI-->>GitOpsProfilesPlugin: Return deployment status
    
    GitOpsProfilesPlugin->>CoreComponents: Update UI with status
    CoreComponents-->>GitOpsProfilesPlugin: UI updated
    
    GitOpsProfilesPlugin-->>App: Plugin rendered
    deactivate GitOpsProfilesPlugin
    
    App-->>User: Display GitOps profiles page
    
    Note over GitOpsProfilesPlugin,CoreComponents: All components now use pinned versions:<br/>- @backstage/config: 0.1.1<br/>- @backstage/core-components: 0.1.0<br/>- @backstage/core-plugin-api: 0.1.0<br/>- @backstage/theme: 0.1.1

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.

[entelligence-ai-pr-reviews]

LGTM 👍

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	form-data@​2.3.3 ⏵ 3.0.1			+1
	has@​1.0.3
	isarray@​2.0.5
	has-proto@​1.0.1
	array-buffer-byte-length@​1.0.0
	gopd@​1.0.1
	node-releases@​2.0.6
	globalthis@​1.0.3
	has-property-descriptors@​1.0.0
	has-tostringtag@​1.0.0
	is-set@​2.0.2
	is-weakmap@​2.0.1
	is-map@​2.0.2
	define-properties@​1.2.0
	functions-have-names@​1.2.3
	es-get-iterator@​1.1.3
	aggregate-error@​3.1.0
	object.fromentries@​2.0.5
	array-flatten@​1.1.1
	path-parse@​1.0.7
	available-typed-arrays@​1.0.5
	is-negative-zero@​2.0.2
	promise.allsettled@​1.0.5
	indent-string@​4.0.0
	object-keys@​1.1.1
	object-is@​1.1.5
	object.getownpropertydescriptors@​2.1.4
	deep-equal@​2.2.1
	get-symbol-description@​1.0.0
	is-date-object@​1.0.5
See 568 more rows in the dashboard

View full report

[socket-security]

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.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		atob@2.1.2 has a License Policy Violation. License: CC-BY-3.0 (package/LICENSE.DOCS) From: storybook/yarn.lock → npm/atob@2.1.2 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/atob@2.1.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		caniuse-lite@1.0.30001378 has a License Policy Violation. License: CC-BY-4.0 (npm metadata) License: CC-BY-4.0 (package/LICENSE) License: CC-BY-4.0 (package/package.json) From: yarn.lock → npm/caniuse-lite@1.0.30001378 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/caniuse-lite@1.0.30001378. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		polished@4.2.2 has a License Policy Violation. License: OFL-1.1 (package/docs/assets/fonts/LICENSE.txt) From: storybook/yarn.lock → npm/polished@4.2.2 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/polished@4.2.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[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!

[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!

[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!

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (^4.5.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.