Skip to content

Releases and artifact status

This page is the release surface for TrustPlane Auth: what the current release contains, what each earlier release added, and the publication status of every artifact type. For download URLs, checksums, and pinning rules, see Install and artifacts.

Current release: v0.2.4 (CLI); adapter & SDKs at v0.2.2

Section titled “Current release: v0.2.4 (CLI); adapter & SDKs at v0.2.2”
Artifact Status
CLI archives Published: trustplane_v0.2.4_<os>_<arch>.tar.gz for darwin/linux × amd64/arm64, with SHA256SUMS and a machine-readable release-manifest.json. No Windows archive in this set.
Adapter image Published: ghcr.io/trustplane-dev/trustplane-auth-adapter:v0.2.2 (public). Pin the digest from the package page.
Helm chart Published: oci://ghcr.io/trustplane-dev/charts/trustplane-auth, version 0.2.2.
Broker image Not published. The broker runs from source builds and the local demo.
Go SDK v0.2.2 — signed tag with a public GitHub release; resolves through normal Go module tooling.
TypeScript SDK 0.2.2 — published to npm with provenance; npm latest points to 0.2.2. Node.js-only.
Python SDK 0.2.2 — published to PyPI through Trusted Publishing.

Checksum verification is mandatory before running any downloaded CLI binary.

Release What it added
v0.2.4 Current CLI release. Workload-profile resolve parses signing_kid/kid; the CLI signs passports under the resolve-issued signing kid (ta-g1-*), fixing missing_issuer_key. CLI only — adapter image and SDKs are unchanged.
v0.2.2 Enrollment fixes: projected proof-file handling (Kubernetes Atomic Writer symlink chains) and enrollment status polling backoff.
v0.2.1 trustplane enroll — Control Trust Anchor enrollment (OIDC JWKS and the other provider profiles), plus enrollment retry/Azure proof-mode safety.
v0.2.0 First v0.2 line release.
v0.1.0-rc.x Historical: established the v0.1 local boundary — passport issuance/verification, transcript-v1 signing, bundles, local broker demo, adapter.

The SDKs (0.2.2 across Go, TypeScript, and Python) are versioned independently of the CLI/runtime releases.

  • A release tag identifies the artifact set that release published — nothing more. Per-profile enrollment availability lives in Trust Anchor source availability.
  • The v0.1 acceptance gate (make v01-acceptance) validates the frozen v0.1 compatibility contract, not the full current release.
  • Missing fields in older audit events are version skew, not corruption — see the Audit guide.