[Snyk] Fix for 1 vulnerabilities

[diegoluisi]

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

Snyk changed the following file(s):

• app/packages/backend/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
	Allocation of Resources Without Limits or Throttling SNYK-JS-WS-17988732

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

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:

🦉 Allocation of Resources Without Limits or Throttling

[diegoluisi]

This set of upgrades includes significant breaking changes in both the Argo CD backend plugin and the Backstage backend-common library, requiring configuration and code updates.

@roadiehq/backstage-plugin-argo-cd-backend 2.13.0 → 3.0.4 (HIGH RISK)

This major version upgrade aligns the plugin with Argo CD 3.0, which introduces several breaking changes to improve security and provide better defaults. Verification and potential configuration changes are required.

Key Breaking Changes:

• Fine-Grained RBAC Enforcement: RBAC policies for update or delete on an application no longer apply to its sub-resources by default. You must define new policies for update/* or delete/* to grant permissions on sub-resources.
• Logs RBAC Enforced by Default: Access to container logs now requires explicit logs, get permissions in your RBAC policies.
• Legacy Repository Configuration Removed: Support for configuring repositories via the argocd-cm ConfigMap has been removed.
• Annotation-Based Tracking: Resource tracking now defaults to using annotations instead of labels. While migration is automatic on the next sync, be aware of a potential edge case where resources can be orphaned if a resource is deleted during the first sync after the upgrade.

Recommendation: Review your Argo CD RBAC policies for update, delete, and logs permissions. After upgrading, perform a sync on applications to migrate to annotation-based tracking.

@backstage/backend-common 0.20.2 → 0.24.1 (HIGH RISK)

This upgrade spans multiple minor versions and introduces breaking changes, most notably the relocation of core functionality.

Key Breaking Changes:

• URL Reader Moved: All URL reader functionality has been moved from @backstage/backend-common to the @backstage/backend-defaults/urlReader package.

Recommendation: You must update all imports that use the URL reader to point to the new package, for example, changing imports from @backstage/backend-common to @backstage/backend-defaults/urlReader where applicable.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.