Repository navigation
Attach the wheel to GitHub releases and document releasing - #2
Merged
Merged
Conversation
Publishing a GitHub release now runs release.yml: it checks that the tag matches the pyproject version, runs pytest, builds the wheel and sdist, smoke-tests the wheel in a clean venv and uploads both to the release. RELEASING.md describes the procedure, and the README shows how to install a release wheel with pipx. The pull request workflow is renamed from ci.yml to default.yml; its job names, which the main ruleset requires, are unchanged. Co-Authored-By: Claude Opus 5.5 <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
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.
Summary
release.yml, run when a GitHub release is published:v) differs from thepyproject.tomlversionpytestuv build→ wheel and sdistmemmap guideandmemmap checkfrom itgh release upload --clobberRELEASING.md: bumping the version through a PR, publishing the release, what the workflow does, installing a release, and recovering from failures.pipx(no uv or checkout needed), and a link toRELEASING.mdunder Develop.ci.ymlrenamed todefault.yml. Job names (test (3.10),test (3.13),build) are unchanged, so themainruleset's required checks still match.Test plan
actionlintpasses on both workflowsuv buildand the wheel smoke test pass locallyuv run pytest: 406 passed🤖 Generated with Claude Code