Raise the mise floor to 2026.7.8#2984
Draft
jeremy wants to merge 1 commit into
Draft
Conversation
Bumps this repo's vendored floor pair — min_version in .mise.toml and mise_min_version in bin/setup — in lockstep with the fleet-wide raise to the first mise containing jdx/mise#11034 (transport-agnostic repo-origin comparison), which the docker-dev-origin v2 setup block relies on. The literal is provisional on the first PUBLISHED qualifying release: the v2026.7.8 tag contains the fix, but its release builds have failed (deterministic macos-arm64 PGO mismatch) — re-literal before merge if a later release publishes first. Setup upgrades mise in place, so un-upgraded machines converge on their next bin/setup run; until then a raised .mise.toml floor errors on every mise invocation in this checkout (announce before landing).
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.
Track B, Train 1 (fleet mise floor raise, lockstep with https://github.com/basecamp/shipyard/pull/149): this repo's vendored floor pair —
min_versionin.mise.tomlandmise_min_versioninbin/setup— bumped 2026.7.5 → 2026.7.8, the first mise containing jdx/mise#11034 (transport-agnostic repo-origin comparison), which Train 2's docker-dev-origin v2 block relies on.Important
Floor literal is provisional — the ruled floor is the first published release containing
95ca0a7b, and none has published yet (mise's release pipeline fails deterministically on a macos-arm64 PGO mismatch; see the shipyard PR). Re-literal before merge if a later release publishes first, and rerun the release/source audit against that version (tracked in the shipyard PR) — the committed audits bind to 2026.7.8, and a later floor can cross new behavior, including 2026.8.0's unconditional precompiled ruby. Gate 3 (installability by installation on curl/brew/Arch) must pass before any merge, and this PR merges only after the shipyard PR lands.Operations
Blast radius is pull-time: once this lands, machines below the floor error on every mise invocation in this checkout (shell hook-env, quickhook hooks, editor integration) until upgraded —
bin/setupconverges them, or one upgrade command per platform. Announce before landing; merge early in a workday.Evidence
test/mise-floor-test --ref ×5(all five app branches): 61/61 — floor declared correctly here, and the vendored floor/upgrade logic remains byte-identical across the fleet at this head.bin/audit-fleet-setup --ref ×5: fleet clean (this PR does not touch the vendored docker-dev-origin block).Precompiled-ruby spike (draft evidence)
Run with the durable harness (
test/ruby-precompiled-spike, shipyard PR) from a clean detached worktree at THIS PR's head, against a source-builtv2026.7.8(de81dc85; binding runs re-execute with the published floor release at the final head):