[Snyk] Security upgrade @backstage/plugin-app-backend from 0.3.73 to 0.3.75

[johnnyhuy]

User description

Snyk has created this PR to fix 1 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
	Expected Behavior Violation SNYK-JS-BACKSTAGEPLUGINAPPBACKEND-8163063	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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

---

PR Type

enhancement, dependencies

---

Description

• Upgraded the @backstage/plugin-app-backend dependency from version 0.3.70 to 0.3.75 to address security vulnerabilities.
• This update is aimed at reducing vulnerabilities as identified by Snyk.

---

Changes walkthrough 📝

	Relevant files
Dependencies	package.json Upgrade @backstage/plugin-app-backend to address vulnerabilities packages/backend/package.json Upgraded @backstage/plugin-app-backend from version 0.3.70 to 0.3.75. Addressed vulnerabilities by updating the package version. +1/-1

---

💡 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]	1, because the PR involves a simple version bump in a package.json file, which is straightforward to review.
🧪 Relevant tests	No
⚡ Possible issues	Possible Dependency Issue: The PR fails to update the yarn.lock file, which is crucial for ensuring that the exact versions of dependencies are used. This could lead to inconsistencies or unexpected behavior in production.
🔒 Security concerns	No

[echohello-codium-ai-pr-agent]

PR Code Suggestions ✨

Category	Suggestion	Score
Best practice	Use a specific version for dependencies to ensure consistent deployments Consider using a more specific version rather than a version range for the @backstage/plugin-app-backend dependency to ensure consistent behavior across different environments and deployments. packages/backend/package.json [25] -"@backstage/plugin-app-backend": "^0.3.75", +"@backstage/plugin-app-backend": "0.3.75", Suggestion importance[1-10]: 8 Why: The suggestion to use a specific version instead of a version range is a good practice for ensuring consistent behavior across different environments and deployments, which can prevent unexpected issues due to version changes.	8