Add end-to-end release automation#80
Open
dwoz wants to merge 2 commits into
Open
Conversation
Detects new Salt point releases (polling saltstack/salt every 10 min), opens a topic/release/<version> PR with generated edits, waits for required PR checks, merges, and runs per-repo post-merge actions.
The previous tag-push step only checked whether the *next* computed tag
name existed, which fails after success: latest=v1.34.0, next=v1.35.0,
which doesn't exist, so we'd push v1.35.0 every poll. The repo's tag
annotation convention ("v<salt_version> release") is the canonical
end-state marker. Gate wait/merge/tag-push on it.
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.
Replaces #78 with a fully automated docs-release pipeline.
Trigger
schedule: every 10 minutesworkflow_dispatch: optionalsalt_versionoverrideWhat it does
saltstack/saltrelease tag (or use the override input).0— LTS bumps require manual edits to lifecycle dates, downloads, etc.topic/release/<version>:tools/supported-versions.json(e.g."3008.0"→"3008.1")Update to Salt <version>, push, open PRv1.33→v1.34.0) with message"v<version> release". Idempotent — skipped if tag already exists. The existingbuild-sphinx-docs.ymlthen builds on tag push.Concurrency / idempotency
concurrency.group: release-automationserializes overlapping runs.Known caveats
GITHUB_TOKENdo not triggerpull_requestworkflows. If you have PR-level CI you want to run before merge, replaceGH_TOKEN: ${{ github.token }}in the PR-creation step with a PAT or GitHub App token stored as a secret.mainthat requires reviews or status checks will block the workflow from merging — needs configuration aligned with the bot identity used.