Releasing Tika gRPC

tika-grpc has no separate release cycle. Its Maven artifact — the slim tika-grpc jar — is built, signed, and deployed to Maven Central as one module in the normal Apache Tika reactor release. Its runnable form is the apache/tika-grpc Docker image. There is no tika-grpc archive on Apache dist by design; see Release Artifacts: What Goes Where for the rationale (the runnable layout bundles every pipes plugin and is too large to publish as a mirror artifact).

What ships where

  • Maven Central — the slim tika-grpc-<version>.jar (plus pom, sources, javadoc, and .asc signatures), for embedding the gRPC server in a Maven/Gradle build. Deployed with the rest of Tika via release:perform.

  • Docker Hub — apache/tika-grpc, the ready-to-run server image, built from a -Pdocker Maven layout and published by .github/workflows/docker-release.yml.

  • Apache dist — nothing. There is no tika-grpc archive on dist.

Release steps

There is nothing gRPC-specific to do during the source release: the jar rides along with the main release — follow Releasing Apache Tika. Publish the Docker image after the vote passes, per Releasing Tika Docker Images.

Post-Release

Covered by the main release guide (next development version, website/download links) and the Docker guide (image tags). Nothing gRPC-specific.