Repository navigation
Publish the tested astral-html sdist before tagging its release - #62
Merged
Merged
Conversation
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.
A maintainer starts a release from main with the version already in the package metadata and changelog. After CI passes, publish the tested source archive for
astral-htmlthrough PyPI trusted publishing, push a lightweight version tag at the tested commit, and publish the matching changelog entry as GitHub Release notes.The publisher accepts only the successful manual workflow in this repository, checks the commit against main, and downloads the artifact from the exact run attempt. PyPI OIDC and GitHub contents-write permissions are assigned to separate jobs.
Record the CI hash-pinning rule in AGENTS.md and apply it to the build toolchain. Verify uv, both Rust toolchains, managed CPython, and the isolated maturin backend before use. The existing zizmor check uses its locked wheel with online audits enabled.
Local validation built the renamed sdist and stable ABI wheel, rejected a bad maturin hash, and exercised changelog selection, prerelease classification, and Git tagging against a local remote.