Release Status & Compatibility
Repository branches, release tags, runtime requirements, and Apache Kafka wire-protocol compatibility targets. The site reads repository status when it builds and uses a cached snapshot if GitHub is unavailable.
Data source: GitHub at build time. Page built: . GitHub checked: .
Repository and package status
The release track describes the tag: 1.0+ is a final tag with major version 1 or higher, Pre-1.0 is a final 0.x tag, Prerelease is another tagged version, and Unreleased has no recorded tag. A version number does not establish operational readiness. Check the candidate qualification evidence and operational limits for your deployment.
| Repository | Release & Branch | Release Track | Target Runtime | Provenance | History |
|---|---|---|---|---|---|
| krabka-broker |
v1.0.8
GitHub at build
|
1.0+ | Linux / macOS / Win (x86_64, aarch64) | SLSA L3 / Sigstore | |
| krabka-protocol |
v0.7.0
GitHub at build
|
Pre-1.0 | Rust (no_std friendly core) | Planned (L3) | |
| krabka-client-rs |
v0.7.1
GitHub at build
|
Pre-1.0 | Rust async tokio | Planned (L3) | |
| krabka-streams-rs |
v0.4.1
GitHub at build
|
Pre-1.0 | Rust stream runtime | Planned (L3) | |
| krabka-streams-go |
v0.2.0
GitHub at build
|
Pre-1.0 | Go 1.27.1+ / Apache Arrow v18 | Planned (L3) | |
| krabka-streams-java |
v1.4.2
GitHub at build
|
1.0+ | Java 17+ / OpenJDK 21 | Maven Central (PGP) | |
| krabka-operator |
v1.0.2
GitHub at build
|
1.0+ | Kubernetes 1.28+ | Planned (L3) | |
| krabka-connect |
v0.4.1
GitHub at build
|
Pre-1.0 | PostgreSQL 14–18 CDC / Rust | Planned (L3) | |
| krabka-cli |
v0.4.6
GitHub at build
|
Pre-1.0 | CLI (cross-platform binary) | GitHub attestations |
Apache Kafka wire compatibility targets
This table lists krabka's wire compatibility targets by Kafka release stream. The targets are checked against Apache Kafka protocol specifications and JVM client suites; consult the implementation status and release evidence before deployment.
| Kafka Release Stream | Wire Protocol Level | KRaft Metadata Layer |
|---|---|---|
| Kafka 2.8 | Compatible | KIP-595 v0 |
| Kafka 3.0 – 3.2 | Compatible | KIP-595 v1 |
| Kafka 3.3 – 3.6 | Compatible | KRaft GA (v2) |
| Kafka 3.7 – 3.9 | Compatible | KRaft Reconfig |
| Kafka 4.0 – 4.3 | Byte-Exact Target | KRaft Native (v4) |
Release artifact provenance and cryptographic verification
Published release artifacts are signed and attested during CI: the broker container image is signed keylessly with Sigstore (Cosign) and carries CycloneDX SBOM and SLSA provenance attestations, and Java packages are signed for Maven Central.
# Verify the broker v1.0.8 image signature (Sigstore, keyless)
IMAGE=ghcr.io/krabka-io/krabka-broker@sha256:1d0dd0d4d721e47866eda23279c37aba11324db222ba8cd7f001554c32e7745f
IDENTITY=https://github.com/krabka-io/krabka-broker/.github/workflows/release.yml@refs/tags/v1.0.8
cosign verify "$IMAGE" \
--certificate-identity "$IDENTITY" \
--certificate-oidc-issuer https://token.actions.githubusercontent.com
# Verify the SLSA v1 provenance attestation on the same image
cosign verify-attestation --type https://slsa.dev/provenance/v1 "$IMAGE" \
--certificate-identity "$IDENTITY" \
--certificate-oidc-issuer https://token.actions.githubusercontent.com
# Verify the CycloneDX SBOM attestation on the same image
cosign verify-attestation --type cyclonedx "$IMAGE" \
--certificate-identity "$IDENTITY" \
--certificate-oidc-issuer https://token.actions.githubusercontent.com
# Verify a Java client artifact signature
ARTIFACT=krabka-streams-1.4.2.jar
gpg --verify "$ARTIFACT.asc" "$ARTIFACT"