Provider Go-bump / notify / release automation#642
Draft
vipsharm wants to merge 1 commit into
Draft
Conversation
Three workflow_dispatch workflows + a shared config and idempotent bump script to manage the Go toolchain version and releases across the kairos-io/provider-* repos from CanvOS: - providers-bump-go: edit Go version everywhere + open PRs per line - providers-notify-prs: email maintainers a summary of open PRs (no merge) - providers-release: next-patch tag + release with diff notes + email Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automates the Go-version upgrade + release flow across the five
kairos-io/provider-*repos, so we don't hand-edit each one on every Go release (ref PE-8936 / PE-8940).What's here
providers-bump-go.yaml(dispatch:go_version,line, optionalticket) — fans out over all providers for the line, edits every Go-version reference, opens a PR against each line's base branch. Does not merge.providers-notify-prs.yaml(dispatch / optional cron:line) — scans each provider for open PRs on the line and emails a summary (links + CI status) to vipin@, santhosh@, abhinav@. Does not merge.providers-release.yaml(dispatch:line,dry_run) — after PRs are merged, computes the next patch tag from the latest tag reachable on each base branch (e.g.v4.8.3→v4.8.4), creates the tag + GitHub Release with notes = commit diff since the last tag, and emails a summary. Defaults todry_run=true.providers.json— single source of truth: each provider's base branch per line (handles the 4.7 mix: kubeadmrelease/v4.7.4, k3s/rke2release/v4.7.2, canonical/nodeadmrc-4.7).bump-go.sh— idempotent editor (go.mod directive, EarthfileARG GOLANG_VERSION, DockerfileFROM golang:, literal workflowgo-version:); skips files a repo lacks. Runnable locally too.Draft until secrets are configured
CanvOS is in
spectrocloud, the providers inkairos-io, soGITHUB_TOKENcan't reach them. Required repo/org secrets (see.github/provider-automation/README.md):PROVIDER_AUTOMATION_TOKEN— App token / fine-grained PAT with contents:write + pull-requests:write on the provider reposMAIL_SERVER,MAIL_PORT,MAIL_USERNAME,MAIL_PASSWORD— SMTP for the email stepsOnce those are set, mark ready for review. The "notify, not merge" choice means a human still merges; auto-merge was intentionally left out.
🤖 Generated with Claude Code