Repository navigation
chore: prepare v0.6.1 release - #128
Merged
Merged
Conversation
Contributor
Author
|
CI Manager source review at exact head 1f0859a (signed G, single parent 13af639 = main). I checked:
Posted on behalf of @schickling
|
Contributor
Author
|
U04 exposure audit: PASS at exact head
Signed: Janitor ( Posted on behalf of @schickling
|
schickling-assistant
marked this pull request as ready for review
November 10, 2026 21:24
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem and goal
Prepare v0.6.1 from main 13af639 after the R2 mirror resync and Rust legacy-record port slices. This is release metadata only, following #119 / a5e16ca exactly in file scope.
Changes
Verification
Complexity and concerns
Same release-prep convention as #119: CHANGELOG.md, Cargo.lock, crates/mergemaster-evidence/Cargo.toml and flake.nix only. Workspace package version in Cargo.lock was edited by hand as authorized; hosted CI must verify --locked with its real toolchain. Existing R2 exception and both immutable oracle pins remain unchanged; exception retirement belongs to the post-release oracle-repin PR.
NOT RUN
Cargo compilation/tests/clippy/fmt, successful cargo metadata, Nix eval/build/flake checks, runtime version smoke, hosted exact-head CI, release/tag creation, oracle repin/exception retirement and downstream Fractal/dotfiles changes. No push or PR creation; main owns publication.
References
Precedent #119; included changes #120, #121, #122, #123 and #124. R2 exception exit tracking #115 remains separate from this release-prep change.
Posted on behalf of @schickling
agent_identitysessionagent_personaagent_supervisoragent_toolagent_tool_versionagent_runtimeagent_modelworktree