Repository navigation
Conversation
…e memory before Releasing was `make publish` with an API token, there were no GitHub releases, the release history lived in the README, and nothing checked that a tag named the version pyproject.toml declares. Pushing a vX.Y.Z tag now refuses to continue unless the tag matches the declared version, the version has a changelog section, the commit is on master and CI passed on it; then builds in isolation, installs the wheel into a clean environment with the checkout kept off sys.path, publishes to PyPI through trusted publishing with signed provenance, and creates the GitHub release from the version's changelog section with the generated contributor list appended. Pre-release tags are marked as such. A manual run rehearses against TestPyPI and stops before the release. The history moves into CHANGELOG.md unchanged, with a Keep a Changelog section above it. A PR that changes picblocks/ or pyproject.toml has to touch CHANGELOG.md or carry the no-changelog label. requirements.txt and pytest.ini fold into pyproject.toml, which already carried the dependencies. The Python floor moves to 3.12, shared across the MCRIT ecosystem.
r0ny123
force-pushed
the
claude/beautiful-ritchie-t8skdt
branch
from
September 24, 2026 10:28
acb0f81 to
4f81c41
Compare
…e release workflow
r0ny123
force-pushed
the
claude/beautiful-ritchie-t8skdt
branch
from
September 24, 2026 10:28
4f81c41 to
72fe131
Compare
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.
Supersedes #5, moved from the fork into familiary as suggested there. The first commit is #5's commit unchanged; the full description (architecture, release jobs, packaging, security, one-time maintainer setup) is on #5.
What the second commit adds, per review on #5
.github/workflows/publish-release.ymlis brought level with smda's current master:Check the milestone for this tag is finishedinverifyandClose the milestone for this taginrelease, byte-identical to smda/purepdb, withissues: readonverifyandissues: writeonrelease.group: release-${{ github.ref }}-${{ github.event_name }}with the comment from ci: scope the release concurrency group to the trigger danielplohmann/smda#353, so a TestPyPI rehearsal no longer queues behind a real run parked on thepypireviewer gate. Two real publishes of one tag still share a group.PYTHON_VERSIONstays at 3.12. After this change, the only differences from smda's workflow are the package name, the CI workflow name, the smoke test and the header comments.