Skip to content

fix: upgrade conventional-actions to node24#46

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

fix: upgrade conventional-actions to node24#46
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 updates the next-version and create-release GitHub Actions; main risk is an unexpected change in versioning/release behavior during the workflow run.

Overview
Updates the CI workflow to use node24-compatible releases of conventional-actions by pinning next-version to v1.1.8 and create-release to v1.0.31 (commit SHAs), replacing the prior @v1 tags for these steps.

Written by Cursor Bugbot for commit 45ff4ec. 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
@antonwinter antonwinter requested a review from a team as a code owner March 18, 2026 19:44
@hanpeter hanpeter merged commit 0d7b3a7 into main Mar 18, 2026
7 checks passed
@hanpeter hanpeter deleted the anton/fix/node24-action-upgrade branch March 18, 2026 20:39
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