Skip to content

ci: rewrite release workflow to be fully GitHub Actions-driven (#25162) (conflicts)#26072

Open
github-actions[bot] wants to merge 1 commit into
release/2.32from
backport/25162-to-2.32
Open

ci: rewrite release workflow to be fully GitHub Actions-driven (#25162) (conflicts)#26072
github-actions[bot] wants to merge 1 commit into
release/2.32from
backport/25162-to-2.32

Conversation

@github-actions
Copy link
Copy Markdown

@github-actions github-actions Bot commented Jun 4, 2026

Backport of #25162

Original PR: #25162 — ci: rewrite release workflow to be fully GitHub Actions-driven
Merge commit: b95697a
Requested by: @f0ssel

Warning

The automatic cherry-pick had conflicts.
Please resolve manually by cherry-picking the original merge commit:

git fetch origin backport/25162-to-2.32
git checkout backport/25162-to-2.32
git reset --hard origin/release/2.32
git cherry-pick -x -m1 b95697a370a80d63a416d5fb686314e3120f754a
# resolve conflicts, then push

@github-actions github-actions Bot requested a review from f0ssel June 4, 2026 18:45
Replace the local interactive release CLI and legacy shell scripts with
a non-interactive Go tool (`scripts/release-action/`) and a rewritten
`release.yaml` workflow. Release managers trigger releases from the
GitHub Actions UI by selecting a branch, picking a release type (`rc`,
`release`, or `create-release-branch`), and optionally providing a
commit SHA.

The Go tool has four subcommands: `calculate-version` (computes next
version from git state), `generate-notes` (release notes from commit log
and PR metadata), `publish` (creates GitHub release with checksums), and
the workflow handles tag creation, branch creation, building, and
downstream publishing.

`scripts/version.sh` fallback now uses `git describe` (nearest ancestor
tag) instead of global latest so dev builds on release branches show the
correct version series.

(cherry picked from commit b95697a)
@f0ssel f0ssel force-pushed the backport/25162-to-2.32 branch from d87bd6f to ae44a6f Compare June 4, 2026 19:10
@f0ssel f0ssel requested a review from jdomeracki-coder as a code owner June 4, 2026 19:10
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.

1 participant