Repository navigation
v0.3.0
Immutable
release. Only release title and notes can be modified.
v0.3.0 - 2026-11-02
Status: Recurrence and Release Integrity Hardening
v0.3.0 adds contract: recurrence/v0 in Rust (sysprims-recurrence) and in
pure Go (go/recurrence). The two implementations agree on the pinned
conformance corpus and on generated rules. This release also hardens the
release ceremony with committed public signing-key pins and fingerprint
anchors, read-only CI artifact builds, immutable GitHub Release promotion,
Sigstore SLSA provenance verification for npm packages, and a Cargo
credential-provider publication gate.
Highlights
- Rust recurrence crate (
sysprims-recurrence): RFC 5545 recurrence rules
undercontract: recurrence/v0with canonical JSON (RFC 8785), SHA-256
digest, canonical RFC 5545 text, and expansion into UTC instants over an
embeddedtzdb2026ebundle. - Pure-Go recurrence module (
go/recurrence): standard-library-only Go
implementation (github.com/3leaps/sysprims/go/recurrence, nocgo) backed
by the same embeddedtzdb2026ebundle and verified byte-for-byte against
the Rust implementation. - Committed release identity and signed tag ceremony: public OpenPGP and
minisign signing keys anddecernorfingerprint anchors are committed in-tree
and verified across the three coordinated release tags (v0.3.0,
bindings/go/sysprims/v0.3.0, andgo/recurrence/v0.3.0). - Read-only release workflows and immutable GitHub Releases: CI release
workflows run with read-only permissions and upload unsigned workflow
artifacts; draft creation, dual signing, immutable release promotion, and
post-publish verification run through maintainer-gated targets. - Cargo credential-provider publication gate:
make release-crates-publish
exports the tagged commit to an isolated directory, verifies tag and release
immutability, checks publishable crate sources, and requires per-crate
interactive confirmation before releasing acrates.iocredential. - Timeout CLI documentation and positioning: clarifies GNU
timeout9.11
and uutils group-by-default behavior versussysprimsdifferentiators
(Windows Job Objects, typed reliability receipts, and MIT/Apache-2.0 library
embedding) and addsdocs/guides/timeout-cli.md.
Recurrence conformance record
| Item | Value |
|---|---|
| Contract | crucible v0.2.0 (0add549dbfc09e4547e2d52d59b633653aa10d71), docs/standards/recurrence-rule-contract.md |
| Conformance corpus | sha256:69387023c21ca147f2dd59c4e47f48447f5eb3ad77121975aab0e4fe0680b35b |
| tzdb | 2026e |
tzdata tzdata2026e.tar.gz |
sha256:b26882805f26aac59d5b222978e6580484b834ccdc98be89df2f05a6dc53a652 |
tzcode tzcode2026e.tar.gz |
sha256:cc3d27ca2a0d8399504551b920970d80af83bfb9c216e8082a15491921935d54 |
TZif bundle tzif-bundle-2026e.bin (446 zones) |
sha256:9291b78ece6c55b5df6bc9e7c51a5a16feb4bffd43b221ed5749260b4e55d705 |
Before tagging, the maintainer rebuilds the bundle from the pinned tzdata and
tzcode with make recurrence-tzdata-check and records the result here:
[ok] tzif-bundle-2026e.bin sha256:9291b78ece6c55b5df6bc9e7c51a5a16feb4bffd43b221ed5749260b4e55d705 (446 zones)
Release Coordinates
- Rust crates:
sysprims-core,sysprims-signal,sysprims-session,
sysprims-proc,sysprims-timeout, andsysprims-recurrenceat0.3.0. - Rust workspace: repository tag
v0.3.0. - Go bindings module: path-prefixed tag
bindings/go/sysprims/v0.3.0on the
same commit (github.com/3leaps/sysprims/bindings/go/sysprims@v0.3.0). - Go recurrence module: path-prefixed tag
go/recurrence/v0.3.0on the same
commit (github.com/3leaps/sysprims/go/recurrence@v0.3.0). - TypeScript:
@3leaps/sysprims@0.3.0, published from the verified core tag.
Cargo Publication Order
sysprims-coresysprims-signalsysprims-sessionsysprims-procsysprims-timeoutsysprims-recurrence
sysprims-cli, sysprims-ffi, and sysprims-ts-napi remain publish = false.
Upgrade Notes
sysprims-recurrence(0.3.0) andgithub.com/3leaps/sysprims/go/recurrence@v0.3.0
are available as standalone recurrence libraries with no host tzdata
dependency.- Release verification assets now include
expected-fingerprints.txtand
expected-fingerprints.ndjsonalongsideSHA256SUMS,SHA512SUMS, and the
public signing keys.