[Snyk] Security upgrade @actions/github from 3.0.0 to 6.0.0

[St0nersdash]

Snyk has created this PR to fix 1 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
	Regular Expression Denial of Service (ReDoS) SNYK-JS-OCTOKITPLUGINPAGINATEREST-8730855	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, focuses on enhancing the project's security posture by upgrading a critical GitHub Actions dependency. The primary goal is to remediate a known vulnerability and ensure the project benefits from the latest security patches and features provided by the updated libraries.

Highlights

• Security Upgrade: This pull request performs a security upgrade of the @actions/github dependency from version 3.0.0 to 6.0.0.
• Vulnerability Fix: The upgrade specifically addresses a 'Regular Expression Denial of Service (ReDoS)' vulnerability identified as SNYK-JS-OCTOKITPLUGINPAGINATEREST-8730855.
• Dependency Updates: As a result of the major version bump for @actions/github, numerous transitive dependencies, particularly within the @octokit ecosystem, have been updated to their latest major versions. Some older, no longer needed, dependencies have also been removed.

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. ↩

[gemini-code-assist]

Code Review

This pull request, generated by Snyk, upgrades @actions/github from 3.0.0 to 6.0.0 to resolve a security vulnerability.

While the upgrade is necessary, it introduces a critical compatibility issue. The new version of @actions/github and its dependencies require Node.js 18 or newer, but the action is configured to run on Node.js 16. This will cause runtime failures.

I've left a detailed comment on package.json explaining the issue and the required fix, which involves updating the action's runtime in action.yml.

[gemini-code-assist]

This upgrade to @actions/github@6.0.0 introduces a critical compatibility issue.

Many of the updated @octokit/* dependencies, which are dependencies of @actions/github@6.0.0, now require Node.js version 18 or higher. For example, the updated package-lock.json shows that @octokit/core@5.2.2 specifies "node": ">= 18" in its engines field.

However, this action is currently configured to run on node16 in action.yml:

runs:
  using: 'node16'
  main: 'dist/setup/index.js'

This version mismatch will cause the action to fail at runtime. To resolve this, you must update the action's runtime in action.yml to node18 or node20.

Recommendation:

Update action.yml to use a newer Node.js runtime. For example:

runs:
  using: 'node18'
  main: 'dist/setup/index.js'

[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
	@​actions/​http-client@​2.1.1 ⏵ 2.2.3			+1

View full report