Skip to content

馃懛 ci(release): share the RST release path - #156

Draft
gaborbernat wants to merge 39 commits into
mainfrom
fix/release-contract
Draft

gaborbernat wants to merge 39 commits into
mainfrom
fix/release-contract

Conversation

@gaborbernat

@gaborbernat gaborbernat commented Oct 20, 2026 •

Copy link
Copy Markdown
Member

This draft moves release preparation, patch validation, distribution checks, and GitHub note rendering to shared Actions. Preparation runs prek before the App key is available. The tag workflow stages a GitHub Release, uploads to PyPI with OIDC, verifies the published files and attestations, then publishes the GitHub Release.

The tracked changelog covers 25 release tags with categorized sections and stable anchors. Fragments retain human credits; GitHub notes also keep first-contributor credits. The required PR check enforces a seven-day cooldown on bot hook updates.

This head pins released github-workflows 1.0.5 and release-creator 0.6.5. The Nab lock selects the five release job groups plus their build and runtime dependencies; package metadata checks and Nab itself stay outside that lock. The lock's selected artifacts, 14 shared Action calls, and prek passed local checks.

The PR remains draft. After the final shared workflow and release-creator releases are reviewed, it needs that released pin, exact-head CI, a release, and backfill of 25 historical GitHub Release bodies.

@gaborbernat gaborbernat added the skip news No user-facing changelog entry needed label Oct 20, 2026
@gaborbernat gaborbernat changed the title 馃懛 ci(release): adopt shared news checks 馃懛 ci(release): share the RST release path Oct 20, 2026
GitHub requires Contents write to generate contributor notes. Keep that call in a tag-restricted job, and build and check the upload files from locked dependencies before publishing.
Stage a matching GitHub Release draft before PyPI upload. On retry, compare the original built files with PyPI, upload only missing files, and verify the complete set before publishing the draft.
Use release-creator 0.5.0 from the project lock. Open weekly release-tool
PRs with the repo-only App so pull request checks run on those changes.
The App needs Pull requests write as well as Contents write.
Use the current shared actions and release-creator 0.5.1 to enforce
the full project lock during release work. Rerun bot PR cooldown checks
daily after their seven-day age gate.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip news No user-facing changelog entry needed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant