Skip to content

fix: upgrade conventional-actions to node24#157

Merged
hanpeter merged 1 commit intomainfrom
anton/fix/node24-action-upgrade
Mar 18, 2026
Merged

fix: upgrade conventional-actions to node24#157
hanpeter merged 1 commit intomainfrom
anton/fix/node24-action-upgrade

Conversation

@antonwinter
Copy link
Copy Markdown
Contributor

@antonwinter antonwinter commented Mar 18, 2026

Summary

Upgrade conventional-actions to node24-compatible releases:

  • conventional-actions/next-versionv1.1.8 (1b3e480)
  • conventional-actions/create-releasev1.0.31 (c025b73)

Node 20 reaches EOL April 2026 and GitHub is forcing migration to node24 by June 2026.

Upstream PRs

Test plan

  • CI passes on this PR

Note

Low Risk
Low risk: CI-only change that bumps/pins GitHub Actions used for versioning and releases; main failure mode is a broken build/release workflow if upstream behavior changed.

Overview
Updates the CI workflow to use node24-compatible conventional-actions by pinning next-version to v1.1.8 and create-release to v1.0.31 (commit SHAs) instead of the floating @v1 tags.

Written by Cursor Bugbot for commit efa2aa5. Configure here.

Node 20 reaches EOL April 2026 and GitHub is migrating Actions
to node24. Update SHA pins to latest releases:

- conventional-actions/next-version v1.1.8
- conventional-actions/create-release v1.0.31

Upstream PRs:
- conventional-actions/next-version#96
- conventional-actions/create-release#8
@hanpeter hanpeter merged commit 6c2c0f1 into main Mar 18, 2026
7 of 8 checks passed
@hanpeter hanpeter deleted the anton/fix/node24-action-upgrade branch March 18, 2026 20:43
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