Repository navigation
Raise the mise floor to 2026.7.10 - #2984
Merged
Merged
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 a mise containing jdx/mise#11034 (transport-agnostic repo-origin comparison), which the docker-dev-origin v2 setup block relies on. Why 2026.7.10: upstream tagged but never published v2026.7.8–v2026.7.10 (release-pipeline failure; v2026.7.11 is the first published release since 7.7). GitHub releases and brew now carry 2026.7.14, but Arch's extra/mise — the Omarchy suite's only channel — was built from the unpublished v2026.7.10 tag, so 2026.7.10 is the highest floor every channel satisfies today (ancestry: compare v2026.7.10...95ca0a7b = behind). 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).
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates Fizzy’s minimum required mise version (“mise floor”) so developer environments will refuse to run mise below the declared version, in support of fleet-wide tooling requirements.
Changes:
- Bump
.mise.tomlmin_versionto a newermisefloor. - Bump
bin/setup’smise_min_versionto match the project floor.
Tip
If you aren't ready for review, convert to a draft PR.
Click "Convert to draft" or run gh pr ready --undo.
Click "Ready for review" or run gh pr ready to reengage.
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| bin/setup | Raises the enforced mise_min_version checked/auto-upgraded by bin/setup. |
| .mise.toml | Raises the repository’s declared min_version for mise config trust/bootstrap. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
jeremy
marked this pull request as ready for review
July 27, 2026 21:07
rhysb27
pushed a commit
to rhysb27/fizzy
that referenced
this pull request
Sep 16, 2026
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 a mise containing jdx/mise#11034 (transport-agnostic repo-origin comparison), which the docker-dev-origin v2 setup block relies on. Why 2026.7.10: upstream tagged but never published v2026.7.8–v2026.7.10 (release-pipeline failure; v2026.7.11 is the first published release since 7.7). GitHub releases and brew now carry 2026.7.14, but Arch's extra/mise — the Omarchy suite's only channel — was built from the unpublished v2026.7.10 tag, so 2026.7.10 is the highest floor every channel satisfies today (ancestry: compare v2026.7.10...95ca0a7b = behind). 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
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.10, a mise containing jdx/mise#11034 (transport-agnostic repo-origin comparison), which Train 2's docker-dev-origin v2 block relies on.Important
Floor resolved:
2026.7.10— upstream tagged but never published v2026.7.8–v2026.7.10 (v2026.7.11 is the first published release since 7.7). GitHub releases and brew now carry 2026.7.14, but Arch'sextra/mise— the Omarchy suite's only install channel — was built from the unpublished v2026.7.10 tag, so 2026.7.10 is the highest floor every channel satisfies today (ancestry:compare v2026.7.10...95ca0a7b=behind; raise again once Arch catches up). The 7.8→7.14 release/source audit is complete (2026-07-27, tracked in the shipyard PR): no task-output or origin-comparison surface changes; the committed audits now bind to 2026.7.10, and the 2026.8.0 unconditional-precompiled-ruby flip remains ahead of the floor. Gate 3 PASSED 2026-07-27 — installability proven by installation on all four channels (macOS curl one-shot self-updated to 2026.7.15, brew bottle 2026.7.14, Arch pacmanextra/mise2026.7.10-1 = exactly the floor, Ubuntu dpkg→mise.run curl 2026.7.15; evidence in shipyardTRACK_B_DRAFT_EVIDENCE/gate3-*-2026-07-27.log). Merge remains gated on the fleet announcement + train GO, 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 (binding evidence, 2026-07-27)
Run with the durable harness (
test/ruby-precompiled-spike, shipyard PR) from a clean detached worktree at THIS PR's head, against the publishedv2026.7.14macos-arm64 release binary (≥ the 2026.7.10 floor; the floor tag itself has no published binary, and the ruby/bootstrap surface is audit-verified unchanged across 7.8→7.14):