[Snyk] Fix for 2 vulnerabilities

[GabLeRoux]

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

Snyk changed the following file(s):

• package.json
• yarn.lock

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.

Vulnerabilities that will be fixed with an upgrade:

	Issue
	Uncaught Exception SNYK-JS-UNDICI-19635210
	HTTP Request Smuggling SNYK-JS-UNDICI-19635212

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

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:

🦉 Uncaught Exception

[GabLeRoux]

These major version upgrades for @actions/core and @actions/tool-cache update the minimum required Node.js runtime for GitHub Actions.

Breaking Changes:

• Node.js Runtime: Both packages now require a Node.js 16 or newer runtime. The previous versions supported Node.js 12. Actions using these packages will fail on runners that still use the end-of-life Node.js 12 runtime.

Impact:

This is an environment-level breaking change. If you are using GitHub-hosted runners, no action is required as they run on supported Node.js versions. If you are using self-hosted runners, you must ensure they are using Node.js 16 or newer.

Source: Package documentation and release notes for the actions/cache v3 action, which indicates a similar Node.js version bump.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 90cc164f-bc57-4329-864f-89eb28642382

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[MrGadget1024]

Breaking Changes:

• Node.js Runtime: Both packages now require a Node.js 16 or newer runtime.

Node20 and earlier are already deprecated and runners are forced up to Node24 already.