Release identity
READY- Version
1.3.3- Release date
October 10, 2026- Source commit
d55e48c- Source tag
v1.3.3
Follow the current GA source identity and publication status, alongside preserved historical archives. Readiness, publication and installation trust are separate facts.
The current GA is tied to its annotated source tag, canonical readiness decision, and authenticated version-matched publication archive.
1.3.3October 10, 2026d55e48cv1.3.3ACC 1.3.3 is the repository's current stable public release. Its report records every implemented readiness gate as PASS, while its manifest binds the package to the complete tagged source identity and readiness evidence.
Supported installation targets are Linux and macOS. Verify package authenticity using independent signer trust before installation.
These records distinguish source identity, readiness and artifact publication for v1.3.3.
Step 1
d55e48c
The v1.3.3 tag identifies the promoted source state.
Step 2
READY
The GA release report records validation and readiness checks as PASS; its authority flags remain false.
Step 3
1322defb4979
The authenticated GA archive is tracked with package, checksum, signature, authenticity, manifest, and release report.
The current GA has a tracked authenticated publication archive. Website deployment and independently established signer trust remain separate concerns.
Current GA · authenticated archive ready
Released October 10, 2026 from d55e48c underv1.3.3 with status READY.
Historical archive
Released September 14, 2026 from 2e3f693 underv1.3.2 with status READY.
Historical archive
Released September 14, 2026 from a816429 underv1.3.1 with status READY.
Historical archive
Released September 13, 2026 from 44e57d6 underv1.3.0 with status READY.
Historical archive
Released September 5, 2026 from ef5d79d underv1.2.1 with status READY.
Historical archive
Released August 25, 2026 from 9625c42 underv1.1.0 with status READY.
Historical archive
Released August 15, 2026 from 23ffa25 underv1.0.0 with status READY.
Keep the package, checksum, manifest, and report together, then follow the version-matched installation workflow.