Skip to content

Release on a tag through trusted publishing, with the checks that were memory before - #6

Open
r0ny123 wants to merge 2 commits into
masterfrom
claude/beautiful-ritchie-t8skdt
Open

r0ny123 wants to merge 2 commits into
masterfrom
claude/beautiful-ritchie-t8skdt

Conversation

@r0ny123

@r0ny123 r0ny123 commented Sep 24, 2026 •

Copy link
Copy Markdown
Collaborator

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.yml is brought level with smda's current master:

  1. Milestone gate: Check the milestone for this tag is finished in verify and Close the milestone for this tag in release, byte-identical to smda/purepdb, with issues: read on verify and issues: write on release.
  2. Concurrency group: 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 the pypi reviewer gate. Two real publishes of one tag still share a group.

PYTHON_VERSION stays 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.

…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
r0ny123 force-pushed the claude/beautiful-ritchie-t8skdt branch from 4f81c41 to 72fe131 Compare September 24, 2026 10:28
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