Skip to content

Release on every push to main - #25

Merged
ethan42 merged 1 commit into
mainfrom
release-on-push
Oct 14, 2026
Merged

ethan42 merged 1 commit into
mainfrom
release-on-push

Conversation

@ethan42

@ethan42 ethan42 commented Oct 14, 2026

Copy link
Copy Markdown
Contributor

Releases no longer need a manual step: publish.yml now runs on every push to main. Each push (each merged PR) builds the PDFs and creates the next patch release (0.1.49, 0.1.50, …).

  • Trigger: push to main replaces release: published. Keeping both would make a hand-made release start a second one. workflow_dispatch stays for a manual rerun.
  • Concurrency group: releases run one at a time in push order, so two quick merges can't compute the same tag.
  • No orphan tags: the separate tag-and-push step is gone. gh release create --target $GITHUB_SHA creates the tag on the pushed commit, after make has succeeded, so a failed build no longer leaves a tag without a release.
  • CLAUDE.md: the CI note now describes the new trigger.

The first release (0.1.49) comes from merging this PR.

Opened from socrates.

Releases were made by hand (a published release or a manual run).
Now each push to main builds the PDFs and creates the next patch
release. A concurrency group keeps releases in push order, and the
tag is created together with the release, after the build, so a
failed build leaves no orphan tag.
@ethan42
ethan42 merged commit 0c58fc8 into main Oct 14, 2026
3 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