Repository navigation
Pin the installer to the 0.3.1 runtime - #11
Merged
Merged
Conversation
install-ladder.sh and check-install.sh pinned c86bf47, the 0.3.0 runtime, so a scripted install still lacked the input and state-boundary fixes that 0.3.1 releases (#9, #10). Move both to 819b7c2, the #10 merge that released 0.3.1, now that it is on main. The invariant block in INSTALL.md is byte-identical at the new pin, so INV_SHA is unchanged. CHECKER_SHA moves with check-install.sh, as it must. The pin test now requires the pinned runtime to report 0.3.1 and to carry the evidence-directory exclusion, and the 0.3.1 CHANGELOG entry records the move. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016m6di8xFVdwwq949mJx9U1
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.
Work package: 0.3.1 patch release, step 2 of 2. Branched from
mainat819b7c2, the #10 merge that released 0.3.1.install-ladder.shandcheck-install.shpinnedc86bf47, the 0.3.0 runtime, so a scripted install still lacked #9's fixes. This moves the pin now that the release commit is onmain. The installer refuses any pin that isn't.scripts/install-ladder.shPINc86bf47→819b7c2;CHECKER_SHAd7b92251…→3a460e1c…scripts/check-install.shPINc86bf47→819b7c2tests/test_install_scripts.pyPINmoved.test_the_pin_installs_the_hardened_releasenow excludes both earlier pins, requires the pinned runtime to reportVERSION = "0.3.1"underevidence-v3.2, and requires it to carry_excluded, #9's evidence-directory fix.CHANGELOG.mdINV_SHAis unchanged, on purpose: the invariant block inINSTALL.mdhashes to282f2117…at bothc86bf47and819b7c2.CHECKER_SHA: equals the sha256 of the committedcheck-install.sh, which changes whenever itsPINline does.Verification
On
8daaec8, against a baseline captured onmainat819b7c2. The baseline gates were green: lint clean, 420 passed / 1 skipped.drift: false.test_the_pin_installs_the_hardened_releasefails;CHECKER_SHA, the installer refuses (6+ install tests fail);check-install.shalone left on the old pin, the conforming-install tests fail.8daaec8): lint, tests-py311, tests-py314 PASS, imported withimport-ci. The pull_request run 36143681138 is also green.sha256:63616894…8bea0e7): 0 blocked required gates, 0 stale, STATE MATCH TRUE, CLEAN CLIMB TRUE, READY FOR HUMAN GATE TRUE.Once this merges: publish the
v0.3.1release in the browser. Under Target → Recent commits, choose this PR's merge commit.Found during review, not changed here:
INSTALL.mdstill says "There are no release tags yet". That has been stale sincev0.3.0. Whether to recommend pinning a tag should wait until tag protection exists on this repo, so I've left it out of this PR.🤖 Generated with Claude Code
https://claude.ai/code/session_016m6di8xFVdwwq949mJx9U1
Generated by Claude Code