Skip to content

馃懛 ci(release): unify pre-commit-uv releases - #190

Draft
gaborbernat wants to merge 44 commits into
tox-dev:mainfrom
gaborbernat:fix/release-contract
Draft

gaborbernat wants to merge 44 commits into
tox-dev:mainfrom
gaborbernat:fix/release-contract

Conversation

@gaborbernat

@gaborbernat gaborbernat commented Oct 20, 2026 •

Copy link
Copy Markdown
Member

Use github-workflows 3.0.0 for App-backed preparation, tagged package validation, PyPI reconciliation, and GitHub Release publication. Release versions come from changelog fragments. The changelog covers 15 tagged releases with user-facing categories, stable anchors, and linked human credits.

The full pylock covers runtime dependencies, build requirements, every declared group, and supported Python and platforms. Release-creator 1.1.0 comes from PyPI; tests, types, and docs still resolve current dependencies. Hook revisions and their Python dependency trees are frozen; the weekly updater refreshes the full lock and hooks.

After review, cut a release and backfill the historical GitHub Release bodies. Four older PyPI versions predate this repository and have no corresponding source history here.

@gaborbernat gaborbernat added the skip news No user-facing changelog entry is needed label Oct 20, 2026
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 gaborbernat changed the title 馃懛 ci(release): validate pre-commit-uv releases 馃懛 ci: unify pre-commit-uv releases Oct 20, 2026
@gaborbernat gaborbernat added enhancement New feature or request bug Something isn't working documentation Improvements or additions to documentation and removed skip news No user-facing changelog entry is needed labels Oct 21, 2026
@gaborbernat gaborbernat changed the title 馃懛 ci: unify pre-commit-uv releases 馃懛 ci(release): unify pre-commit-uv releases Oct 21, 2026
Stage only missing distributions and verify the full PyPI file set before
creating the GitHub Release. A retry can resume a partial upload while
changed files still fail verification.
Require a matching GitHub draft before PyPI staging. The zero-missing
retry path must not publish a Release when draft staging failed.
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

bug Something isn't working documentation Improvements or additions to documentation enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant