[Snyk] Fix for 2 vulnerabilities

[johnnyhuy]

User description

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

Snyk changed the following file(s):

• 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	Score
	Prototype Pollution SNYK-JS-BACKSTAGEPLUGINCATALOGBACKEND-8023177	641
	Protection Mechanism Failure SNYK-JS-BACKSTAGEPLUGINTECHDOCSBACKEND-8023175	526

---

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:

🦉 Prototype Pollution

---

PR Type

Bug fix, Dependencies

---

Description

This PR addresses two vulnerabilities in the project's dependencies by upgrading the following packages:

• Upgraded @backstage/plugin-catalog-backend from ^1.25.0 to ^1.26.0 to fix the Prototype Pollution vulnerability.
• Upgraded @backstage/plugin-techdocs-backend from ^1.10.10 to ^1.10.13 to fix the Prototype Pollution vulnerability.

---

Changes walkthrough 📝

	Relevant files
Dependencies	package.json Upgrade dependencies to fix vulnerabilities                            packages/backend/package.json Upgraded @backstage/plugin-catalog-backend from ^1.25.0 to ^1.26.0 Upgraded @backstage/plugin-techdocs-backend from ^1.10.10 to ^1.10.13 +2/-2

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[echohello-codium-ai-pr-agent]

PR Review 🔍

⏱️ Estimated effort to review [1-5]	2, because the PR involves simple version updates in the package.json file, which are straightforward to review. However, the reviewer needs to ensure that these updates do not introduce compatibility issues with other packages.
🧪 Relevant tests	No
⚡ Possible issues	Dependency Mismatch: The PR fails to update the yarn.lock file, which is necessary for ensuring that the specified versions of dependencies are used. This could lead to inconsistencies and potential errors during runtime.
🔒 Security concerns	No

[echohello-codium-ai-pr-agent]

PR Code Suggestions ✨

Category	Suggestion	Score
Best practice	Pin the version of @backstage/plugin-catalog-backend to a specific minor version to ensure stability Consider pinning the version of @backstage/plugin-catalog-backend to a specific minor version instead of using the caret (^) version range. This can help avoid unexpected issues due to automatic updates to newer minor versions, which might introduce breaking changes or new bugs. packages/backend/package.json [31] -"@backstage/plugin-catalog-backend": "^1.26.0", +"@backstage/plugin-catalog-backend": "1.26.0", Suggestion importance[1-10]: 8 Why: Pinning the version can help avoid unexpected issues from automatic updates, which is a good practice for maintaining stability in dependencies.	8
Maintainability	Use a fixed version for @backstage/plugin-techdocs-backend to avoid unintended updates Update the version of @backstage/plugin-techdocs-backend to a specific patch version without using the caret (^) to ensure that the exact intended version is used, preventing automatic updates that could potentially introduce instability. packages/backend/package.json [45] -"@backstage/plugin-techdocs-backend": "^1.10.13", +"@backstage/plugin-techdocs-backend": "1.10.13", Suggestion importance[1-10]: 8 Why: Using a fixed version prevents automatic updates that could introduce instability, which is important for maintaining a stable environment.	8