Siglake 0.2.1

Siglake 0.2.1 rebuild from the corresponding renamed historical release commit 08cbeaa6d508eba1a4a6810de4002e004b8686b9.

Version changelog

Public container images:

• Engine: ghcr.io/siglake/siglake@sha256:4ddeaf85826c18d6f225d433cac3488fa2b4ab118db51496340ef910764d6892 (also tagged 0.2.1).
• Operator: ghcr.io/siglake/siglake-operator@sha256:446f78f81b5ef52e6fccad477ff94ef13339c2acefb165b508b90f01f5eb2b1e (also tagged 0.2.1).

Verified on 2026-10-08 with anonymous registry access: both binaries match the release version and source commit; all four entrypoints launch; the operator emits the renamed CRD; isolated Compose services start; 100 OTLP events commit with exact rows and grouped counts; committed rows survive a query-server restart; owned containers, networks and volumes are removed.

This is basic rename verification, not a new full burn-in, Kubernetes upgrade qualification, or side-aggregate qualification.

Smoke evidence and immutable image digests

Siglake 0.2.0

Siglake 0.2.0 rebuild from the corresponding renamed historical release commit dc9ace08ba4dd06a391b4b77aba982e8a4d6e9b6.

Version changelog

Public container images:

• Engine: ghcr.io/siglake/siglake@sha256:eb71337eb3c0740b9a74a5a01ba53c85342a5bbbd408e410b888d5343f8c2e53 (also tagged 0.2.0).
• Operator: ghcr.io/siglake/siglake-operator@sha256:4235a7edba4e27041dac8c35660e8a88c922eb93632bc4abe5e46c7fcd18962c (also tagged 0.2.0).

Verified on 2026-10-08 with anonymous registry access: both binaries match the release version and source commit; all four entrypoints launch; the operator emits the renamed CRD; isolated Compose services start; 100 OTLP events commit with exact rows and grouped counts; committed rows survive a query-server restart; owned containers, networks and volumes are removed.

The smoke test substitutes pinned public MinIO fixtures for withdrawn historical dependencies; the original release source is unchanged. Details are retained in the verification record.

This is basic rename verification, not a new full burn-in, Kubernetes upgrade qualification, or side-aggregate qualification.

Smoke evidence and immutable image digests

Siglake 0.1.0

Siglake 0.1.0 rebuild from the corresponding renamed historical release commit 65a0be9c61a202cdbbf84cda6cc4202b643cd4b5.

Version changelog

Public container images:

• Engine: ghcr.io/siglake/siglake@sha256:56db77fe6abf5d1ba902a6faec3f69f3d7582cd2baae4bab53ea6d7a88808f34 (also tagged 0.1.0).
• Operator: ghcr.io/siglake/siglake-operator@sha256:2dd4ce30efc6b388038654d7d046c303883ec0fe97ba09cf40b76f5f7b370bbd (also tagged 0.1.0).

Verified on 2026-10-08 with anonymous registry access: both binaries match the release version and source commit; all four entrypoints launch; the operator emits the renamed CRD; isolated Compose services start; 100 OTLP events commit with exact rows and grouped counts; committed rows survive a query-server restart; owned containers, networks and volumes are removed.

The smoke test substitutes pinned public MinIO fixtures for withdrawn historical dependencies; the original release source is unchanged. Details are retained in the verification record.

This is basic rename verification, not a new full burn-in, Kubernetes upgrade qualification, or side-aggregate qualification.

Smoke evidence and immutable image digests