Skip to content

chore(release): bump to v0.22.0#310

Merged
avrabe merged 1 commit into
mainfrom
chore/release-v0.22.0
Jun 30, 2026
Merged

chore(release): bump to v0.22.0#310
avrabe merged 1 commit into
mainfrom
chore/release-v0.22.0

Conversation

@avrabe

@avrabe avrabe commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

v0.22.0 — "Deployable TSN synthesis"

Cuts v0.22.0 with three shipped features (clean-room audited GO):

Req PR What
REQ-NC-PLP-MIN-001 #307 Authoritative per-flow NC bound = min(PLP, TFA)
REQ-WRPC-BINDING-003 #308 Verify Actual_Connection_Binding resolves to a bus
REQ-TSN-SYNTH-QBV-GUARDBAND-001 #309 Guard-band-aware 802.1Qbv GCL splitting (deployment-sound)

Release handling — adopts rivet 0.22's release flow

  • The three features carry a top-level release: v0.22.0 field and are advanced to verified (each now has a verifies link from its TEST-* feature). rivet release status v0.22.0 → ✓ cuttable (every scoped artifact verified/accepted).
  • Stale fields.release entries removed on the migrated artifacts.
  • Cross-version verified: CI rivet v0.4.3 (merge gate) and v0.7.0 (verification gate) both PASS with unchanged warning counts (112 / 120) — the migration introduces zero new diagnostics.

Scope correction (clean-room blocker)

REQ-TSN-SYNTH-CQF-LONGLINK-001 moved to v0.23.0 via rivet release move — its committed spec is unsound (the delay interval inverts on long links once the buffer clause activates). It's deferred for a sound cycle-quantized rewrite; a SPEC-UNDER-REVISION marker + the corrected model are recorded in the artifact.

Bump

Workspace 0.21.00.22.0 (Cargo.toml, Cargo.lock, vscode-spar/package.json). cargo build --workspace green.

Falsification

If the guard-band synthesizer's emitted GCL were not deployment-sound, a class would miss its deadline under the §8.6.8.4 overrun model — the K=1 anchor (guard_band_k1_equals_sync_error_at_eps_g) and the full-schedule self-cert would fail. They pass.

🤖 Generated with Claude Code

v0.22.0 — "Deployable TSN synthesis". Three features shipped since v0.21.0:
- REQ-NC-PLP-MIN-001 (#307) — authoritative per-flow NC bound = min(PLP, TFA).
- REQ-WRPC-BINDING-003 (#308) — verify Actual_Connection_Binding resolves to a bus.
- REQ-TSN-SYNTH-QBV-GUARDBAND-001 (#309) — guard-band-aware 802.1Qbv GCL
  splitting (deployment-sound; charges the §8.6.8.4 transmission-overrun guard).

Release-handling: adopts rivet 0.22's `release` flow. The three features carry a
top-level `release: v0.22.0` field and are advanced to `verified` (each now has a
`verifies` link from its TEST-* feature); `rivet release status v0.22.0` reports
cuttable (every scoped artifact verified). Stale `fields.release` entries removed
on the migrated artifacts. Cross-version-checked: CI rivet v0.4.3 (merge gate) and
v0.7.0 (verification gate) both PASS with unchanged warning counts.

Scope correction (clean-room audit blocker): REQ-TSN-SYNTH-CQF-LONGLINK-001 moved
to v0.23.0 via `rivet release move` — its committed spec is unsound (delay interval
inverts on long links) and is deferred for a sound cycle-quantized rewrite; a
SPEC-UNDER-REVISION marker + the corrected model are recorded in the artifact.

Bumps workspace 0.21.0 → 0.22.0 (Cargo.toml, Cargo.lock, vscode-spar/package.json).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@avrabe avrabe enabled auto-merge (squash) June 30, 2026 19:30
@github-actions

Copy link
Copy Markdown

Rivet verification gate

20/20 passed

count
Passed 20
Failed 0
Skipped (no steps) 0

Filter: (and (= type "feature") (or (has-tag "v093") (has-tag "v0100")))

Failed artifacts

(none)

Updated automatically by tools/post_verification_comment.py. Source of truth: artifacts/verification.yaml.

@codecov

codecov Bot commented Jun 30, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@avrabe avrabe merged commit 9148635 into main Jun 30, 2026
32 of 33 checks passed
@avrabe avrabe deleted the chore/release-v0.22.0 branch June 30, 2026 22:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant