Skip to content

release: v0.34.0 — adapter inlining (#304) + multi-memory isolation commitment (#300)#307

Merged
avrabe merged 1 commit into
mainfrom
release/v0.34.0
Jun 23, 2026
Merged

release: v0.34.0 — adapter inlining (#304) + multi-memory isolation commitment (#300)#307
avrabe merged 1 commit into
mainfrom
release/v0.34.0

Conversation

@avrabe

@avrabe avrabe commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

Release commit for v0.34.0: version bump 0.33.0→0.34.0 + CHANGELOG + SR-42 verified.

The feature code already merged via #306 (identity-trampoline adapter inlining #304; multi-memory isolation commitment #300/ADR-4; #298/#299 secondary foundation). This PR carries only the release metadata.

  • Version: 0.33.0 → 0.34.0 (workspace.package)
  • CHANGELOG: [0.34.0] entry with falsification statement
  • SR-42 implemented → verified

On merge + green main CI → tag v0.34.0 (triggers release.yml signing).

Refs #304, #300, #298. Plan SR-42/43/44.

…i-memory isolation commitment (#300/ADR-4)

Bundles the work merged via #306:
  #304 identity-trampoline adapter inlining (SR-42, verified);
  #300 multi-memory structural isolation committed (ADR-4) + Auto explicit
  attested-build warning + N=3 hardening; #298/#299 reclassified secondary
  (inert oracle/verdict foundation rides along). Release plan landed:
  SR-42 [v0.34.0], SR-43 [v0.35.0 #305], SR-44 [v0.36.0 #303].

Release-time reconciliation: SR-42 implemented → verified (its runtime/
clean-room oracle is green; passed the PR-time Mythos delta-pass gate 4/4
NO FINDINGS).

Readiness (V-model): version 0.33.0 → 0.34.0; CHANGELOG [0.34.0] with
falsification statement; full meld-core suite green per-commit; #306
required gates all green (Test/Clippy/Format/LS-N/Mythos). No admin merge.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

LS-N verification gate

57/57 approved LS entries verified

count
Passed (≥1 test, all green) 57
Failed (≥1 test failure) 0
Missing (no ls_*_NN_* test found) 0

Approved loss-scenarios.yaml entries are expected to have a
regression test named ls_<letter>_<num>_* (e.g. LS-A-11
ls_a_11_*). The gate runs each prefix via cargo test --lib --no-fail-fast and aggregates pass/fail/missing.

Failed LS entries

(none)

Missing regression tests

(none)

Updated automatically by tools/post_verification_comment.py.
Source of truth: safety/stpa/loss-scenarios.yaml.

@avrabe avrabe merged commit 2826c2f into main Jun 23, 2026
17 checks passed
@avrabe avrabe deleted the release/v0.34.0 branch June 23, 2026 06:56
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