Skip to content

chore(ci): bump actions to Node 24-compatible versions#1

Merged
cadolbeau-absyss merged 1 commit into
mainfrom
chore/bump-actions-node24
May 26, 2026
Merged

chore(ci): bump actions to Node 24-compatible versions#1
cadolbeau-absyss merged 1 commit into
mainfrom
chore/bump-actions-node24

Conversation

@Cadolbeau

Copy link
Copy Markdown
Contributor

Summary

Bumps the three GitHub Actions used in our workflows to their latest major versions, all targeting Node.js 24:

Action Before After Released
actions/checkout @v4 @v6 Nov 2025
azure/setup-helm @v4 @v5 Mar 2026
softprops/action-gh-release @v2 @v3 Apr 2026

Why

GitHub announced (see GitHub Changelog – Sept 19, 2025):

  • June 2nd, 2026 — Node 20 actions are forced to run on Node 24 by default
  • September 16th, 2026 — Node 20 is removed from runners

Our last CI run displayed the warning for the 3 actions above (all on Node 20). Bumping now avoids surprises during the forced migration in 7 days.

Test plan

  • All 3 actions have released a Node 24-compatible major
  • No breaking change in workflow inputs (verified release notes)
  • CI passes green on this PR
  • Release workflow still works on next tag

After merge, the next v0.1.x tag will exercise the bumped softprops/action-gh-release@v3 end-to-end.

GitHub will force all Node 20 actions to run on Node 24 starting
June 2nd, 2026, and Node 20 will be removed from runners on
September 16th, 2026.

Bumps the three actions used in our workflows to their latest
major versions, which target Node 24:

- actions/checkout@v4 -> v6
- azure/setup-helm@v4 -> v5
- softprops/action-gh-release@v2 -> v3

@cadolbeau-absyss cadolbeau-absyss left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

@cadolbeau-absyss cadolbeau-absyss merged commit f0de659 into main May 26, 2026
4 checks passed
@cadolbeau-absyss cadolbeau-absyss deleted the chore/bump-actions-node24 branch May 26, 2026 17:31
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.

2 participants