Repository navigation
release: v0.22.3 - #212
Merged
Merged
release: v0.22.3#212
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
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.
Weekly release train.
0.22.3(bump:patch)v0.22.2— 1 commit(s)Merging this publishes
0.22.3to PyPI, which cannot be undone — a release can beyanked by hand, never replaced. Check the changelog section above before merging.
Merge with squash so the commit subject stays
release: v0.22.3; the tag workflowkeys on that subject, and will do nothing if it is reworded.
A PR opened with
GITHUB_TOKENhas its CI run created inaction_requiredrather thanstarted. The job below approves it so the required checks report against this PR.
🤖 Generated with Claude Code