Bump version to 0.2.2#16
Merged
Merged
Conversation
Member
Author
|
Once the 0.2.2 release is complete, could you please yank the affected 0.2.0 release? |
vbkaisetsu
approved these changes
May 30, 2026
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
2 participants
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.
This PR uploads python-vibrato version 0.2.2.
Sorry, I accidentally issued the 0.2.1 tag without updating the version to 0.2.1. As a result, the artifact release failed. Because of this, we must re-upload the artifacts as 0.2.2, and it seems that the following actions are needed:
vibrato-0.2.0-cp310-abi3-manylinux_2_5_i686.manylinux1_i686.whlwere published by mistake. (see https://docs.pypi.org/project-management/yanking/)Also, as a preventive measure, I added a version consistency check to CI.