Repository navigation
Prepare Runtime v0.36.0 release documentation - #298
Conversation
Co-authored-by: Codex (gpt-6.1-sol) <noreply@openai.com> Signed-off-by: kikashy <kikashy@hotmail.com>
|
Independent review accepted this exact documentation at No open P1/P2. The53-line CHANGELOG addition correctly describes cumulative functionality since publishedv0.34, preserves the existing heldv0.35 entry, and distinguishes prototype0.0.2, explicitly selected proposed-draft candidate1.0.0, and Review/unadopted RFC status. Exact changelog hash Focused static/base/hash/link/whitespace checks passed; the independent reviewer reused them without tests/builds/network repetition. Existing Runtime CI39165392059, native Runner CI39270753757 and real combined Desk CI39275718610 remain source evidence. Required PR CI and tag-time archives/native smoke/checksums/attestations are separate pending gates. Runtimev0.35.0 remains held; no publication, OCI/MCP action, live installation or enrollment is approved by this review. |
|
🎉 Thank you for your contribution to Judgment Pack! If you’d like another task, choose a path that interests you: |
Material-decision impact: documented-claim; review: #298 (comment)
Prepare Runtime v0.36.0 notes covering the Policy functionality since the last published v0.34.0: the retained prototype and explicit proposed-draft candidate, their CLI/MCP surfaces, and compatibility and authority limits. The source was already reviewed and tested; this PR changes CHANGELOG.md only.
The existing v0.35.0 draft/tag remains held at5157249. This does not adopt the Policy RFC, change default Core/prototype behavior, publish a release/image/registry entry, or install anything. Candidate1.0.0 and prototype0.0.2 remain explicit distinct formats.
Validation: focused file/base/hash, preserved old changelog, SemVer, whitespace/UTF-8 and note checks passed. Reuse source Runtime CI39165392059 and actual combined acceptance Desk CI39275718610; required PR CI and eventual tag/archive verification remain gates. Independent Codex review uses the maintainer’s standing temporary different-vendor waiver; it is same-vendor review.