[Snyk] Security upgrade @backstage/backend-common from 0.23.2 to 0.23.3

[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
	Regular Expression Denial of Service (ReDoS) SNYK-JS-FASTXMLPARSER-7573289	559

---

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:

🦉 Regular Expression Denial of Service (ReDoS)

---

PR Type

Bug fix, Dependencies

---

Description

• Upgraded @backstage/backend-common dependency from version 0.23.2 to 0.23.3 to address a security vulnerability (Regular Expression Denial of Service - ReDoS).
• Note: Users of Yarn's zero-installs feature need to run yarn to update the contents of the ./yarn/cache directory.

---

Changes walkthrough 📝

	Relevant files
Dependencies	package.json Upgrade `@backstage/backend-common` to fix security vulnerability packages/backend/package.json Upgraded @backstage/backend-common dependency from version 0.23.2 to 0.23.3. +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	No
🔒 Security concerns	No

[echohello-codium-ai-pr-agent]

PR Code Suggestions ✨

Category	Suggestion	Score
Best practice	Pin the version of a dependency to avoid potential issues with automatic updates Consider pinning the version of @backstage/backend-common to 0.23.3 instead of using the caret (^) version range. This can help ensure that the exact version intended is used, avoiding potential issues with automatic updates that might introduce breaking changes or bugs. packages/backend/package.json [19] -"@backstage/backend-common": "^0.23.3", +"@backstage/backend-common": "0.23.3", Suggestion importance[1-10]: 9 Why: Pinning the version of @backstage/backend-common can help ensure stability by avoiding unintended breaking changes from automatic updates. This is a best practice for dependency management.	9