Skip to content

Release on merge: the version decides, the tag comes from CI - #8

Merged
markope merged 3 commits into
mainfrom
ci-on-pr
Oct 24, 2026
Merged

markope merged 3 commits into
mainfrom
ci-on-pr

Conversation

@markope

@markope markope commented Oct 24, 2026

Copy link
Copy Markdown
Contributor

Prepares the CI-on-PR process: checks only on pull requests into main; the merge of a release pull request (version bump, title release <name> v<x>) publishes the image and then sets the tag; an unchanged version is a no-release pull request whose merge starts nothing; release pull requests run a release dry run. Backward compatible: a pushed version tag still releases, so repositories keep working until they move to the new callers (templates).

Marko Petzold added 3 commits October 24, 2026 20:27
… on release PRs

- release-intent: no title marker any more. An unchanged version is a
  no-release pull request (any title that does not read like a release);
  a rising version is a release pull request titled `release <name> v<x>`.
- release-image: no tag job; it needs read rights only, so a release
  pull request can run it as a dry run (every platform build, no push).
- release-tag: the tag of every release, a job of its own after all image
  jobs, so a tag always means "in the registry".
- templates: release.yml = image + tag; ci-go.yml adds release-build (the
  repository's release.yml as a dry run on release pull requests); ci-ok
  accepts it skipped only on no-release pull requests.
- README: the two pull request kinds, recovery from a failed release run,
  central logic with thin per-repository callers.
…153 note

The caller templates call the repository's own release.yml, which exists only
once a template is copied; .github/actionlint.yaml ignores exactly that
message for templates/workflows. TITLE in release.sh intent comes from the
environment.
@markope
markope merged commit c1d5581 into main Oct 24, 2026
61 checks passed
@markope
markope deleted the ci-on-pr branch October 24, 2026 19:13
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