Repository navigation
👷 ci(release): validate notes before PyPI - #292
Draft
gaborbernat wants to merge 59 commits into
Draft
gaborbernat wants to merge 59 commits into
gaborbernat wants to merge 59 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
The release-only pylock omitted other dependency groups and narrowed the usable Python range. Export all selections from uv's project resolution and keep release installs scoped to their group.
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.
Use github-workflows #3 and release-creator #11 for named fragments, protected release preparation, tagged artifact checks, and GitHub notes. Preparation runs
prekbefore the repository-scoped App pushes a commit and tag. The tag workflow stages a matching GitHub Release draft, uploads only missing exact files to PyPI on retry, verifies the complete PyPI set, then publishes the draft. Contents-write jobs use the numeric-tagreleaseenvironment.The changelog covers every PyPI version. The Python 3.11 support entry in 0.3.0 comes from PR #31. The full lock includes build and package-check tools;
hatch-fancy-pypi-readmeprovides working changelog and contribution links in PyPI metadata. The shared workflow remains in a draft PR; release-creator 0.5.1 is locked from PyPI.The required PR check enforces a seven-day cooldown on pre-commit.ci hook updates using the live head and PR update time.
Release jobs now install only the tool groups they use from the full project lock.