Repository navigation
👷 ci(release): validate notes before PyPI - #292
Draft
gaborbernat wants to merge 64 commits into
Draft
gaborbernat wants to merge 64 commits into
gaborbernat wants to merge 64 commits into
Conversation
gaborbernat
added
bug
gaborbernat
enabled auto-merge (squash)
October 19, 2026 18:18
gaborbernat
disabled auto-merge
October 19, 2026 18:21
gaborbernat
force-pushed
the
fix/release-changelog-format
branch
from
October 19, 2026 20:32
f62fedb to
c878e06
Compare
gaborbernat
changed the title
gaborbernat
changed the title
Render notes and validate the build before PyPI publication. Keep the GitHub Release writer free of checkout and third-party tool installation.
Freeze hook revisions and mdformat plugins while letting the weekly updater refresh exact plugin pins after the cooldown.
gaborbernat
changed the title
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
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.
This draft moves release preparation and the tagged release to shared Actions. Preparation selects a version from fragments, runs
prek, validates the patch without the App key, then uses the repository App to push the commit and tag. The tag workflow builds and checks the distribution, stages a GitHub Release, uploads to PyPI through OIDC withskip-existing, verifies the published files, and publishes the GitHub Release.The changelog covers each PyPI version, including the Python 3.11 support added in PR #31. The PyPI description uses
hatch-fancy-pypi-readmeto link the changelog and contribution guide. A separate required check enforces the hook update cooldown.This head pins released github-workflows 1.0.5 and release-creator 0.6.5. The Nab lock selects only the five release job groups plus build and runtime dependencies. The selected lock passed the exact released Action's check and an independent PyPI metadata check; all 14 shared Action inputs match 1.0.5, and
prekpassed.The draft still needs the final shared release pin and exact-head CI, then a release and historical GitHub Release body backfill.