[Snyk] Security upgrade @backstage/plugin-scaffolder-backend from 1.24.1 to 1.25.1

[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
	Server-side Request Forgery (SSRF) SNYK-JS-BACKSTAGEPLUGINSCAFFOLDERNODE-8454494	501

---

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:

🦉 Server-side Request Forgery (SSRF)

---

PR Type

enhancement, dependencies

---

Description

• Upgraded the @backstage/plugin-scaffolder-backend dependency from version 1.24.0 to 1.25.1 in package.json.
• This upgrade addresses a security vulnerability related to Server-side Request Forgery (SSRF).
• Users of Yarn's zero-installs feature should run yarn to update the cache directory.

---

Changes walkthrough 📝

	Relevant files
Dependencies	package.json Upgrade @backstage/plugin-scaffolder-backend to address vulnerabilities packages/backend/package.json Upgraded @backstage/plugin-scaffolder-backend from version 1.24.0 to 1.25.1. Addressed a security vulnerability by updating the dependency. +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 the package.json file, which is straightforward and requires minimal time to review.
🧪 Relevant tests	No
⚡ Possible issues	Possible Bug: The PR description mentions that the yarn.lock file failed to update. This needs to be addressed to ensure that the correct versions of dependencies are used and to maintain the integrity of the dependency tree.
🔒 Security concerns	No

[echohello-codium-ai-pr-agent]

PR Code Suggestions ✨

Category	Suggestion	Score
Best practice	Pin the version of @backstage/plugin-scaffolder-backend to a specific version to avoid unexpected upgrades Consider pinning the version of @backstage/plugin-scaffolder-backend to 1.25.1 instead of using the caret (^) version range. This can help ensure that the specific, vetted version of the package is used, reducing the risk of automatically upgrading to newer versions that might not have been tested or could introduce breaking changes. packages/backend/package.json [38] -"@backstage/plugin-scaffolder-backend": "^1.25.1", +"@backstage/plugin-scaffolder-backend": "1.25.1", Suggestion importance[1-10]: 8 Why: Pinning the version of a dependency can prevent unexpected issues caused by automatic upgrades to newer versions that may introduce breaking changes. This suggestion is a good practice for maintaining stability in the project.	8