Release on push to main when the declared version has no tag yet - #4
Merged
Merged
Conversation
The release workflow now also runs on pushes to main that touch the version, the release notes or itself, and creates the tag and GitHub release for pyproject.toml's version when that tag does not exist. Manual dispatch stays available. The release title is the level-1 heading of docs/releases/v<version>.md. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011hwnef5pyjkdpQ6deZJYDD
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
2 participants
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.
Release prep for v0.4.0, second step.
The release workflow added in #3 can only be started by hand (
workflow_dispatch). This makes it also run on pushes tomainthat touchpyproject.toml,docs/releases/**, or the workflow itself. It reads the version frompyproject.toml; if tagv<version>does not exist yet, it creates the tag and the GitHub release, with the title taken from the level-1 heading ofdocs/releases/v<version>.mdand the rest of that file as the body. If the tag already exists it does nothing, so the workflow is idempotent and a version bump plus notes in one pull request is a release.Merging this pull request pushes to
mainand triggers the first run, which cutsv0.4.0("The Site Archive").🤖 Generated with Claude Code
https://claude.ai/code/session_011hwnef5pyjkdpQ6deZJYDD
Generated by Claude Code