Skip to content

SWI-3723 [Snyk] Security upgrade @actions/github from 6.0.1 to 8.0.1#6

Open
bwappsec wants to merge 3 commits intomainfrom
snyk-fix-540e88da0c678296a517e2e99b952a3b
Open

SWI-3723 [Snyk] Security upgrade @actions/github from 6.0.1 to 8.0.1#6
bwappsec wants to merge 3 commits intomainfrom
snyk-fix-540e88da0c678296a517e2e99b952a3b

Conversation

@bwappsec
Copy link
Copy Markdown

snyk-top-banner

Snyk has created this PR to fix 5 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 Score
high severity Improper Handling of Highly Compressed Data (Data Amplification)
SNYK-JS-UNDICI-15518068
  169  
high severity Uncaught Exception
SNYK-JS-UNDICI-15518070
  169  
medium severity HTTP Request Smuggling
SNYK-JS-UNDICI-15518061
  118  
medium severity CRLF Injection
SNYK-JS-UNDICI-15518072
  61  
medium severity Allocation of Resources Without Limits or Throttling
SNYK-JS-UNDICI-14943963
  38  

Breaking Change Risk

Merge Risk: Medium

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:

🦉 Allocation of Resources Without Limits or Throttling
🦉 Uncaught Exception
🦉 CRLF Injection

@bwappsec
Copy link
Copy Markdown
Author

Merge Risk: Medium

This is a major version upgrade from v6 to v8 of @actions/github.

Breaking Changes:

  • Node.js Version: The minimum required Node.js version has been increased to 20. The previous version supported Node.js 18. GitHub Actions workflows using an older Node.js version will need to be updated.
  • Octokit Dependencies: Core @octokit dependencies have been updated to new major versions.

Recommendation:
Ensure your GitHub Actions runners are configured to use Node.js 20 or a later version. Verify that any custom scripts interacting with the Octokit API are compatible with the latest dependency versions.

Source: Package RELEASES.md.

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

@bwappsec
Copy link
Copy Markdown
Author

bwappsec commented Apr 13, 2026

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues
Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@bwappsec bwappsec changed the title [Snyk] Security upgrade @actions/github from 6.0.1 to 8.0.1 SWI-3723 [Snyk] Security upgrade @actions/github from 6.0.1 to 8.0.1 Apr 13, 2026
jgutierrezglez and others added 2 commits April 13, 2026 14:47
The Snyk PR generated the lockfile with an older Yarn format (v6) which
causes CI to fail with YN0028 (lockfile would be modified). Regenerated
with Yarn 4.8.1 to produce the correct v8 lockfile.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants