ci: semantic-version releases from PR labels, with the latest release's bundles refreshed on every merge - #87
Merged
nicolasbisurgi merged 1 commit intoSep 29, 2026
Conversation
…h the latest release's bundles on every merge A merge to master whose tests pass builds the Windows, Linux x86-64 and Linux arm64 bundles. With a release:major, release:minor or release:patch label, the version is bumped, committed and tagged vX.Y.Z, the bundles are built from the tag, and the release takes its notes from the CHANGELOG.md section. Without a label, the new bundles replace those on the latest release. A version newer than every release is released as it stands, so 2.0.0 releases as v2.0.0. Each bundle carries a BUILD_INFO.txt with its version and commit. The decisions live in .github/scripts/release.py, covered by tests/test_release_script.py. Tests and the PR build run only when code changes, and a PR builds Linux x86-64 only. Releases publish only from cubewise-code/optimus-py. CONTRIBUTING.md and the PR template explain the labels. Co-Authored-By: Claude Opus 5.5 (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.
Releases become semantic versions chosen by a label on the merged PR, and the latest release's bundles stay current between versions.
How it works
When a PR is merged to
masterand Tests pass, Build Executable builds the Windows, Linux x86-64 and Linux arm64 bundles. What happens next depends on the PR's label:release:major,release:minororrelease:patch: the version is bumped inpyproject.tomlandsrc/optimuspy/__init__.py, committed tomasterand taggedvX.Y.Z. The bundles are built from that tag, and the releasevX.Y.Zis created with them. Its notes are the## X.Y.Zsection ofCHANGELOG.md, or GitHub's generated notes when there is none.vX.Y.Zrelease. Thebuild-<sha>releases are never touched.Details:
master, with any release label, becomesv2.0.0rather than3.0.0.BUILD_INFO.txtwith its version and commit.CHANGELOG.mdand the workflow files count as code). A PR builds Linux x86-64 only, and a docs-only merge neither builds nor releases.cubewise-code/optimus-py, or from the repository named by theRELEASE_REPOSITORYvariable.The decisions are in
.github/scripts/release.py, covered bytests/test_release_script.py.CONTRIBUTING.mdand the new PR template explain the labels. The installation docs point at the Releases page.Checks
python -m pytest -q: 473 passed, 10 live tests deselected.python -m mkdocs build --strict: clean.build.yml,test.ymlanddeploy-site.yml.After the merge
The
optimuspy2dot0triggers stay until the v2 merge tomaster, so the site keeps deploying from this branch until then.🤖 Generated with Claude Code