Skip to content

ci: backport release signing changes to release/2.39 (#32209, #32211) - #32224

Merged
sreya merged 2 commits into
release/2.39from
backport/32209-32211-to-2.39
Nov 16, 2026
Merged

sreya merged 2 commits into
release/2.39from
backport/32209-32211-to-2.39

Conversation

@sreya

@sreya sreya commented Nov 16, 2026

Copy link
Copy Markdown
Collaborator

Backports release workflow changes from main so releases cut from release/2.39 use the current signing flow:

Each commit is a git cherry-pick -x of the original commit on main. After these, .github/workflows/release.yaml matches main exactly.

Conflicts: none; both commits applied cleanly (auto-merged .github/workflows/ci.yaml, Makefile, and go.mod without conflicts).

Validation: go build ./scripts/gpgkms/ and go test ./scripts/gpgkms/ pass; bash -n scripts/sign_with_gpg.sh scripts/sign_darwin.sh scripts/build_go.sh passes; both changed workflows parse as valid YAML; git diff origin/main -- .github/workflows/release.yaml is empty.

Requested by @sreya.

@github-actions

Copy link
Copy Markdown
Contributor

👋 Hey @sreya!

This PR is targeting the release/2.39 release branch, but its title does not start with fix: or fix(scope):.

Only bug fixes should be cherry-picked to release branches. If this is a bug fix, please update the PR title to match the conventional commit format:

fix: description of the bug fix
fix(scope): description of the bug fix

If this is not a bug fix, it likely should not target a release branch.

@sreya
sreya marked this pull request as ready for review November 16, 2026 02:48
@sreya
sreya requested a review from a team November 16, 2026 02:48
@sreya
sreya merged commit 9981ea8 into release/2.39 Nov 16, 2026
62 of 63 checks passed
@sreya
sreya deleted the backport/32209-32211-to-2.39 branch November 16, 2026 02:56
@linear-code

linear-code Bot commented Nov 16, 2026

Copy link
Copy Markdown

SEC-1432

This branch had an error being deployed

1 failed deployment
docs-preview — 4cb9330d Deployed Nov 16, 2026 by sreya via cleanup #81
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