Repository navigation
Prepare Voyager 2.2.1 release - #153
Merged
Merged
Conversation
stephen29xie
approved these changes
Oct 16, 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
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.
Prepare Voyager 2.2.1 for a fresh coordinated release using the publishing fixes already merged into main. Version 2.2.0 is already on PyPI and its Maven upload failed.
Bump Python and Maven versions, update README installation examples, and regenerate the checked-in Java and Python API documentation for 2.2.1.
Replaces the recovery approach in #152. After merge, create the 2.2.1 GitHub release from the merged commit to run the normal publishing pipeline.
Validation:
javadoc:jarsucceeded using JDK 17, with existing missing-comment warnings.git diff --check.No library code changed.