Skip to content

v0.2.8

Choose a tag to compare

@github-actions github-actions released this 07 Nov 20:34
· 15 commits to main since this release
Immutable release. Only release title and notes can be modified.
v0.2.8
3b0647d

Release v0.2.8

Defines durable-record (v0 and v1) RFC 3339 instant validation profiles and finite JSON Schema subset admission, deprecates durable-record/v0 for new producers, specifies the durable-record/v1 writer-owned incomplete-append abort boundary and runtime.incarnation_allocation, adds the draft opslead role, and adds workflow supply-chain, key-expiry, and local-path hygiene gates.

This release tightens durable-record (v0 and v1) timestamp validation and
schema-dialect admission, deprecates durable-record/v0 for new stream
production while preserving historical v0 verification, and codifies the
durable-record/v1 writer-owned incomplete-append abort boundary and
incarnation allocation modes (runtime.incarnation_allocation). It also adds
the supplemental draft opslead role prompt and introduces repository gates
for GitHub Actions SHA/digest pinning, release signing-key expiration horizons,
and local-path content hygiene.

Highlights

durable-record (v0 and v1) timestamp profiles, v0 deprecation, and finite JSON Schema subset

  • RFC 3339 instant validation profiles. Updates
    docs/standards/durable-record-contract.md,
    docs/standards/durable-record-v1-contract.md,
    scripts/rfc3339-instant.py, scripts/validate-durable-record-fixtures.py,
    and scripts/test-durable-record-v1-controls.py to enforce ASCII-only
    ([0-9]) RFC 3339 instant validation across every v0 and v1 timestamp
    position: year bounds 0001–9999 inclusive (0000 and UTC year
    underflow/overflow refused), proleptic Gregorian calendar validation,
    unconditional :60 leap-second refusal, and microsecond fractional precision
    (v1 requires 6 fractional digits with Z; v0 accepts Z or bounded
    ±HH:MM offsets < 24:00 and no nonzero digit beyond the sixth fractional
    place).
  • Per-position stage evaluation and v0 source/ancestor checks. Documents
    the per-position Stage 3 (shape) vs. Stage 4 (instant_spelling /
    semantic) evaluation trace, validates v0 journal at timestamps on every
    entry of observed v0 continuation source and ancestor streams (including
    entries beyond cut_seq), validates received v1 reconciliation
    attempted_at, window_covers_from, and window_covers_until positions, and
    adds AST position-deletion mutation witnesses for every timestamp check.
  • Finite JSON Schema Draft 2020-12 subset admission. Enforces a closed
    finite allowlist of JSON Schema Draft 2020-12 keywords across all v0 and
    v1 schemas and rejects sibling assertion keywords alongside $ref.
  • Deprecation of durable-record/v0 for new producers. Marks
    schemas/durable-record/v0/contract.json
    as "status": "deprecated" with "superseded_by": "contract: durable-record/v1".
    Existing v0 schemas, fixtures, and validator controls remain supported for
    verifying historical v0 streams and v1 continuations.

durable-record/v1 writer-owned incomplete-append abort boundary and runtime.incarnation_allocation

  • NDJSON framing and writer-owned incomplete-append abort gate. Clarifies in
    docs/standards/durable-record-v1-contract.md
    that every committed NDJSON journal entry line L ends with a single LF
    (0x0A) without CR (0x0D) and that an unterminated final line (including
    k = L - 1 missing only the trailing LF) refuses at Stage 1 as ingest.
    Codifies the completion gate for rolling back a provably incomplete write
    (0 <= k < L) in-process under continuous reader and writer exclusion:
    verifying SameFile descriptor identity on the truncate handle before
    truncating, truncating back to the recorded prior-cut byte offset, syncing
    the journal file and parent directory, verifying post-truncate byte length via
    fstat, and re-validating the prior complete cut (1..cut_seq).
  • Fail-closed handle poisoning and restart semantics. Requires any
    indeterminate commit (k == L followed by a failed fsync, EIO, uncertain
    write count, or lost exclusion) or any failure during the abort completion
    gate to poison the journal handle in-process against further appends or
    dependent body operations until reopen, and defines the disjunctive reopen
    oracle across crash points around truncate and fsync.
  • Incarnation allocation modes (runtime.incarnation_allocation). Adds
    optional runtime.incarnation_allocation ("effect_dependent" |
    "prewrite_durable_ledger", permitted only when
    deletion.external_bodies == "supported") to
    schemas/durable-record/v1/stratum-profile.schema.json,
    paired with schema reject fixtures and faultpoint controls in
    scripts/test-durable-record-v1-controls.py.

Operations Lead opslead role (1.0.0, draft)

  • Adds supplemental config/agentic/roles/opslead.yaml
    (1.0.0, status: draft, category governance, domains governance,
    coordination, and automation) and
    docs/catalog/roles/opslead.md for accountable
    stewardship of estate operating procedures, seat and identity lifecycle
    records, and operating-convention baselines, acting through explicit grants
    for any privileged step while handing coordination-tool operation to
    dispatch and credential, asset, and security-hardening operations to
    secops or a human custodian.

Workflow supply-chain pinning, signing-key expiration horizon, and local-path hygiene

  • Workflow supply-chain and permission gate (scripts/test-workflow-pins.sh).
    Verifies that every uses: reference in .github/workflows/*.yml is pinned
    to a 40-hex commit SHA with a # v... version comment, every container
    image carries an immutable @sha256: digest, and top-level and job-level
    permissions blocks stay within read-only defaults except for the release tag
    attestation job.
  • Release signing-key expiration horizon (check_release_key_expiry).
    Extends scripts/release-env.sh (wired into
    scripts/release-derive-anchors.sh and scripts/release-verify-anchors.sh
    and tested in scripts/test-release-identity.sh) to inspect
    docs/security/release-signing-keys.asc and config/release/pgp-key-id.txt,
    failing closed when the primary key or pinned signing subkey is expired,
    revoked, invalid, missing an expiration timestamp on derive, or carrying
    ambiguous binding signatures, and emitting a warning on stderr when
    expiration is within 30 days.
  • Local-path content hygiene (scripts/content-check.py). Scans git-tracked
    files for accidental local home paths, macOS/Windows/Linux temporary paths,
    and file:// URLs targeting local user directories, wired into make check.

What a release carries

A crucible release is a GPG-signed annotated Git tag. It publishes no assets,
so there are no SHA256SUMS or SHA512SUMS files to verify. See
docs/security/README.md.

Upgrade notes

  • For durable-record adopters: durable-record/v0 is now marked
    "status": "deprecated" ("superseded_by": "contract: durable-record/v1")
    for new stream production; new streams should target durable-record/v1 while
    retaining v0 readers/validators for historical streams and continuation
    sources. Verify that implementation timestamp parsers enforce ASCII-only digits
    ([0-9]), reject year 0000 (including after UTC offset conversion), and
    reject :60 leap seconds across both v0 and v1.
  • For durable-record/v1 external-body stores: Profiles with
    deletion.external_bodies: "supported" may now declare
    runtime.incarnation_allocation ("effect_dependent" or
    "prewrite_durable_ledger"; defaults to "effect_dependent" when omitted).

References