Prepare 0.9.0 release - #43
Merged
Merged
Conversation
Bump the crate version (pyproject reads it via maturin) and turn the CHANGELOG's Unreleased section into the dated 0.9.0 section that the release job extracts verbatim as the GitHub release notes.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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
1 participant
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.
Bumps
Cargo.tomlto 0.9.0 (Cargo.lockfollows) and dates the CHANGELOG section.Release notes extraction verified locally: the release job's
awkpulls 59 lines for## [0.9.0], starting at the summary paragraph and ending before## [0.8.0].After merging, the tag push is the manual step:
This is the first release through the trusted-publishing + auto-GitHub-release job (#41), so watch the
Releasejob.PYPI_API_TOKENcan be deleted from repo secrets once it succeeds.