Skip to content

[release-1.0] Maintain fork release branches and unify publishing - #109

Merged
EItanya merged 1 commit into
release-1.0from
backport/release-1.0-shared-release-workflow
Oct 30, 2026
Merged

EItanya merged 1 commit into
release-1.0from
backport/release-1.0-shared-release-workflow

Conversation

@EItanya

@EItanya EItanya commented Oct 30, 2026 •

Copy link
Copy Markdown

Backport #106 to release-1.0 so 1.0 releases use the shared workflow for fork GHCR images and Helm charts, with binaries attached to the GitHub release. This also brings over the skill for maintaining and backporting patches across branches.

Unchanged cherry-pick of a57b0844b0b6cb9543f421ec5db2b4a6fbe1b701 onto 926dab7f859e66c93350a3cbb80881d0494cdbaf.

Fork release flow
flowchart LR
    tag["Release tag"] -->|checkout| images["Publish versioned images"]
    images -->|success| charts["Publish three Helm charts"]
    charts -->|success| draft["Build binaries and create draft release"]
Loading

Validated with go test -race -p=1 ./..., hack/verify-all.sh, three shuffled race-test runs of the affected packages, actionlint, skill validation, and website content generation. Independent review confirmed the patch matches the source commit.

Used Codex to prepare, validate, and review the backport.

(cherry picked from commit a57b084)
Signed-off-by: Eitan Yarmush <eitan.yarmush@solo.io>
@EItanya EItanya mentioned this pull request Oct 30, 2026
1 of 2 tasks
@EItanya
EItanya merged commit 71b1f9e into release-1.0 Oct 30, 2026
8 checks passed
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