[dylanrb123]

Prepare Voyager 2.2.2 with the Maven Central bundle fix. Release 2.2.1 signs and uploads successfully, but Central rejects its bundle with Bundle has content that does NOT have a .pom file: com/spotify/voyager.

Upgrade central-publishing-maven-plugin from 0.8.0 to 0.12.0, which fixes staging metadata cleanup with Maven 3.10.0. Bump both Python and Java to 2.2.2, update README installation examples, and regenerate the checked-in API docs. After merge, create the 2.2.2 GitHub release from the merged commit to run the normal publishing pipeline.

Reference: https://central.sonatype.org/publish/publish-portal-maven/#0120-13-oct-2026
Failed job: https://github.com/spotify/voyager/actions/runs/38964841648/job/117197764440

Validation:

• Ran the Maven deploy lifecycle locally with plugin 0.12.0, a temporary encrypted signing key, and -DskipUpload=true, deliberately seeding staging with the metadata files that caused rejection. The ZIP contained all 24 expected artifact/signature/checksum files under the correct version directory and excluded staging metadata. All four signatures were independently verified, along with the five native library entries.
• Parsed Python TOML and Maven XML; package versions and generated documentation identify 2.2.2.
• Built and installed the 2.2.2 Python package; Sphinx HTML generation succeeded.
• Maven javadoc:jar succeeded with existing missing-comment warnings.
• git diff --check passed.

No production secrets were read and no registry upload was attempted.