Skip to content

2026.01

Latest

Choose a tag to compare

@shsingh shsingh released this 26 Oct 04:16
· 12 commits to main since this release
2026.01
2f3eaa1

G6 — the 2026.01 release-notes body: the DRAFT (the comment carries the body; no release, no tag)

Draft status: this = the release-notes BODY as a draft for the operator's cut. The release object and the bare tag = the operator's later signed manual step (ADR-0003). The draft reads main at ae4e2189 at write time (2026-10-25T13:17Z). Full CI at the tip = green.


2026.01 (GA)

Status: the cut carries the five TLS-termination leaves + the three trunk verdict lanes below. The gate receipts = issue #275 before the tag. The bare 2026.01 tag = the operator's signed manual step.

The shipped surface (per the merged lane rows)

Lane Surface Ref
TR-203 L1 The UDP/QUIC kernel abuse class: the flow rows, the tarpit, the ban push PR #271
TR-203 L2 The QUIC-ingress lab topology: the probes P4/P7/P8-h3 live PR #273
TR-203 L3 The engine inline H3 listener (opt-in --h3-listen; the alt-svc advertisement) PR #272
TR-203 L4 The PQC termination profile: X25519MLKEM768 on each termination surface the repo controls PR #270
TR-203 L5 The JA4/PQC corpus + the QUIC-Initial read design PR #268
TR-194 The stage stamps: the FlowEvent bitmap, the verdict arrays, the span link (leaves 1–3) PR #245 + PR #274
TR-198 The JWT claims stage at S3 (the request.auth vocabulary) PR #269
TR-199 The protocol conformance rejects (the framing classes) PR #267

Each row = merged code + its recorded runs. The run refs = the lane receipt set (the TR-203 lane parent).

The rc2 and rc3 capabilities stay shipped. The list: CRS parity, CEL budgets, the rate and ban tiers, the DoS detectors. The list continues: the challenge hop, the OTel pipeline, the residue gate. The academy ships 5 of 5 modules with runnable labs.

Upcoming features (the named post-GA boundaries)

  • Re-encryption: the TLS-inspection egress leg of the TLS-termination lane. The standing post-GA boundary (the spec's phasing record).
  • The PQC signature migration (the CA cert chain): the 2026.02/03 trains. The key exchange = shipped in this cut. The signatures = not.
  • The socket class 2 extension (the CEL fast-path class): TR-196 builds past this cut. The socket-plane surface = the route-marking class, on the spec's tracked-evaluation record.

Verify a release asset (the release rule's block)

gh attestation verify <asset> -R trishula-dev/trishula

Every release asset carries the SLSA provenance/v1 attestation and the SPDX 2.3 SBOM. Both = Rekor-backed. The verify command = the same on every future tag. The per-asset receipts post on #275. The recipe = Recipe 12. The SHA in checksums.txt pins the bytes; the attestation pins the producer. Both must hold.

No capability claim in this draft states a run the record does not carry.

The rows above = the PRs + the recorded runs in the receipts.