[Snyk] Fix for 2 vulnerabilities

[St0nersdash]

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

Snyk changed the following file(s):

• package.json
• package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Predictable Value Range from Previous Values SNYK-JS-FORMDATA-10841150	863
	Regular Expression Denial of Service (ReDoS) SNYK-JS-OCTOKITREQUEST-8730853	666

---

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)

[gemini-code-assist]

Summary of Changes

Hello @St0nersdash, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, aims to enhance the project's security posture by upgrading two key npm dependencies: @actions/cache and @actions/github. These upgrades are specifically designed to resolve a critical 'Predictable Value Range' vulnerability and a medium 'Regular Expression Denial of Service (ReDoS)' vulnerability, ensuring the project utilizes more secure and up-to-date library versions.

Highlights

• Dependency Upgrades: Upgraded the @actions/cache dependency from version ^3.1.4 to ^4.0.0.
• Dependency Upgrades: Upgraded the @actions/github dependency from version ^3.0.0 to ^6.0.0.
• Vulnerability Fixes: Addressed a critical 'Predictable Value Range from Previous Values' vulnerability (SNYK-JS-FORMDATA-10841150) by updating dependencies.
• Vulnerability Fixes: Addressed a medium 'Regular Expression Denial of Service (ReDoS)' vulnerability (SNYK-JS-OCTOKITREQUEST-8730853) by updating dependencies.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​actions/​github@​3.0.0 ⏵ 6.0.0			+1	-4
	@​actions/​http-client@​2.1.1 ⏵ 2.2.3			+1
	@​actions/​core@​1.10.1 ⏵ 1.11.1	+1
	@​actions/​cache@​3.1.4 ⏵ 4.0.0			+6	+1
	typescript@​3.8.3 ⏵ 3.9.10

View full report

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, updates @actions/cache and @actions/github to new major versions to fix security vulnerabilities. However, these updates introduce significant breaking changes. The current codebase is not compatible with these new versions, which will break the caching functionality of this action and potentially other parts of the action. The code, including tests, needs to be updated to align with the new APIs before this PR can be merged.

[gemini-code-assist]

This PR introduces major version bumps for @actions/cache (v3 to v4) and @actions/github (v3 to v6), which include breaking changes that are not handled in the current codebase.

@actions/cache v4.0.0 Breaking Change:

The cache.restoreCache() function in v4 returns a Promise<number | undefined> (the cache ID) instead of a Promise<string | undefined> (the cache key) as it did in v3. The existing code in src/cache-restore.ts and src/cache-save.ts is not compatible with this change.

Specifically:

• In src/cache-restore.ts, the cacheKey variable now holds a cache ID, but it's used as if it were a cache key string for logging and for saving to state. The log message Cache restored from key: ${cacheKey} is now misleading.
• In src/cache-save.ts, the logic to prevent re-saving an existing cache is broken. It compares the primaryKey (a string) with the state (which is now a cache ID), so primaryKey === state will always be false, causing the cache to be re-saved unnecessarily on every run with a cache hit.
• The tests in __tests__/cache-restore.test.ts are also outdated, as they mock cache.restoreCache to return a string key.

@actions/github v6.0.0 Breaking Change:

This is also a major version bump with several breaking changes between v3 and v6. For example, the github.context.repo object structure has changed. While the files in this PR don't show its usage, other files in the repository (like src/installer.ts) likely use it and will need to be updated.

To fix this, the code needs to be updated to be compatible with the new APIs of these packages. Simply bumping the versions will break the action's caching functionality.