[Snyk] Fix for 5 vulnerabilities

[diegoluisi]

Snyk has created this PR to fix 5 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
	Inefficient Algorithmic Complexity SNYK-JS-JSYAML-17900054
	Infinite loop SNYK-JS-TAR-17909068
	Incorrect Type Conversion or Cast SNYK-JS-TAR-17909104
	Allocation of Resources Without Limits or Throttling SNYK-JS-TAR-17909152
	Uncaught Exception SNYK-JS-TAR-17909225

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
🦉 Uncaught Exception

[diegoluisi]

This release includes major version upgrades with significant breaking changes for @roadiehq/backstage-plugin-argo-cd-backend and node-gyp, along with important deprecations in Backstage core packages that require developer action.

@roadiehq/backstage-plugin-argo-cd-backend from 2.13.0 to 4.3.1 (HIGH)

This is a major version upgrade from v2 to v4. While specific changelogs for this package are not available, major version jumps in the Argo CD ecosystem often introduce breaking changes. For example, Argo CD v3 introduced breaking changes to RBAC and removed legacy repository configurations. [48] Due to the significant version jump and lack of detailed release notes for this specific plugin, there is a high risk of breaking changes.

Recommendation:

• Review your Argo CD integration and configurations carefully.
• Test the integration in a non-production environment to identify any potential issues with authentication, RBAC, or application fetching.

node-gyp from 9.4.1 to 11.0.0 (HIGH)

This upgrade includes two major version bumps with significant breaking changes related to the build environment:

• v11.0.0: Drops support for Node.js 16.
• v10.0.0: Requires Python 3.12 or newer for projects that use it. [32, 41]

Recommendation:

• Ensure your development and CI/CD environments are using a supported version of Node.js (>=18) and Python (>=3.12).

@backstage/backend-common from 0.20.2 to 0.24.1 (MEDIUM)

As part of the migration to the new Backstage backend system, several functionalities have been deprecated and moved to other packages. [29] Key changes include:

• URL reader functionality has been moved to @backstage/backend-defaults/urlReader. [26]
• Database types, helpers, and implementations have been moved to @backstage/backend-defaults. [29]
• The TokenManager is deprecated in favor of coreServices.auth, coreServices.httpAuth, and coreServices.userInfo.

Recommendation:

• Update your imports to use the new locations for these functionalities to avoid future breakages.

@backstage/plugin-permission-node from 0.7.27 to 0.8.1 (MEDIUM)

This upgrade includes the deprecation of createPermissionIntegrationRouter in favor of the new PermissionsRegistryService. [31, 34]

Recommendation:

• Migrate your permission backend setup to use the new PermissionsRegistryService to align with the new Backstage backend system.

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