feat: v0.8.0 — self-update: explicit, verified, old-verifies-new - #19
Merged
Conversation
REQ-UPDATE-001 verified. varve self-update checks the latest release, verifies the successor with the running binary against the pinned trust root, and replaces atomically; unsigned/impostor/unparseable all refuse and leave the current binary untouched (mutation-checked). No passive network calls. Release sums now signed with the labeled provisional rolling root pending the ceremony (dual-signed migration release planned). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019TNtfRjLNhEz82G2ggeeNu
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
1 participant
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.
REQ-UPDATE-001 (
rivet release status v0.8.0: cuttable).varve self-update [--check] [--to]— the running binary verifies its successor against the pinned root before atomic replacement; unsigned releases, impostor signatures and unparseable versions refuse, leaving the current binary untouched (tested against a release-API double, verification-skip mutation-checked). No phone-home. Release sums now signed with the labeled provisional rolling root per the interim decision; ceremony release will be dual-signed.🤖 Generated with Claude Code
https://claude.ai/code/session_019TNtfRjLNhEz82G2ggeeNu