[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
	Relative Path Traversal SNYK-JS-BACKSTAGEPLUGINTECHDOCSBACKEND-8022917	641
	Missing Release of Resource after Effective Lifetime SNYK-JS-INFLIGHT-6095116	631

---

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:

🦉 Relative Path Traversal

---

PR Type

Bug fix, Dependencies

---

Description

This PR addresses two vulnerabilities in the yarn dependencies of the project by upgrading specific packages:

• Upgraded @backstage/backend-common from ^0.23.3 to ^0.25.0 to fix SNYK-JS-BACKSTAGEPLUGINTECHDOCSBACKEND-8022917
• Upgraded @backstage/plugin-techdocs-backend from ^1.10.10 to ^1.10.13 to fix SNYK-JS-INFLIGHT-6095116

---

Changes walkthrough 📝

	Relevant files
Dependencies	package.json Upgrade dependencies to fix vulnerabilities                            packages/backend/package.json Upgraded @backstage/backend-common from ^0.23.3 to ^0.25.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 straightforward dependency updates in the package.json file. The changes are minimal and only involve version bumps for two dependencies, which typically does not require extensive review unless there are known compatibility issues.
🧪 Relevant tests	No
⚡ Possible issues	Dependency Compatibility: The updated versions of "@backstage/backend-common" and "@backstage/plugin-techdocs-backend" need to be checked for compatibility with other project dependencies and the overall project configuration.
🔒 Security concerns	No

[echohello-codium-ai-pr-agent]

PR Code Suggestions ✨

Category	Suggestion	Score
Best practice	Pin the version of @backstage/backend-common to a specific version Consider pinning the version of @backstage/backend-common to a specific version rather than using a caret (^) version range. This can help ensure consistent behavior and compatibility, especially in production environments. packages/backend/package.json [19] -"@backstage/backend-common": "^0.25.0", +"@backstage/backend-common": "0.25.0", Suggestion importance[1-10]: 8 Why: Pinning the version can help ensure consistent behavior and compatibility, especially in production environments. This is a good practice to avoid unexpected issues due to version changes.	8
Enhancement	Update @backstage/plugin-techdocs-backend to the latest version Update the version of @backstage/plugin-techdocs-backend to a newer version if available, to include the latest security patches and features. packages/backend/package.json [45] -"@backstage/plugin-techdocs-backend": "^1.10.13", +"@backstage/plugin-techdocs-backend": "^1.10.14", # Assuming 1.10.14 is the latest version Suggestion importance[1-10]: 3 Why: While keeping dependencies up-to-date is important, the suggestion assumes a newer version exists without verifying it. Additionally, the PR already updates the version, so this suggestion is less impactful.	3