flux-controller-patch-releases

Automating Flux controller patch releases involves fetching repository state, creating release branches, updating go.mod and kustomization.yaml, committing with signed messages, and opening PRs for integration to reduce manual toil.

Changelog generation for a Flux patch release works by drafting a consolidated entry based on PRs merged into the release series branch since the previous tag. This tracks upstream changes across controllers for the release preparation workflow.

Updating version references for a GitOps patch release requires modifying root go.mod and config/manager/kustomization.yaml with new tags. The process commits these changes with signed messages and pushes branches to origin to trigger release workflows.

You need to create a release branch from a Flux release series branch when preparing a patch release. This isolates changes, allowing you to update version references, draft consolidated changelogs, and open PRs for release integration back to main.

The Flux patch release workflow requires signed commits for tagging. It pushes release preparation branches and signed tags to origin, ensuring release integrity and triggering downstream release workflows automatically.

Automating patch releases for Flux controllers is limited to the upstream Flux controller workflow scope. It handles release series branches, version updates in go.mod and kustomization.yaml, and signed commits, but does not manage major release branching or cross-cutting infrastructure changes.