fix(tooling): bump mise min_version to 2026.7.11 for the monorepo_root key - #888
Merged
scottschreckengaust merged 4 commits intoSep 14, 2026
Merged
Conversation
… key PR #874 renamed `experimental_monorepo_root` -> `monorepo_root`, but that key did not exist until mise 2026.7.9 (jdx/mise#11052, 2026-07-16). Any contributor on `2026.2.6 <= mise < 2026.7.9` therefore got a per-prompt `unknown field: monorepo_root` warning. Raise the floor to match the config the repo actually requires, turning a silent warning into a clear upgrade gate. Closes #887 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The four workspace configs (cdk/agent/cli/docs) declare the same `min_version` floor as the root and are meant to move together. Keep all five uniform at 2026.7.9 so the monorepo presents one coherent floor. Refs #887
…ver published The `monorepo_root` key first landed in the 2026.7.9 tag (jdx/mise#11052), but 2026.7.8, 2026.7.9, and 2026.7.10 were tagged and never published to the release/install channels (release-pipeline issue); their changes shipped in 2026.7.11 (published 2026-07-20). Pinning the floor to a version nobody can `mise use`/install would just trade a warning for an unsatisfiable requirement, so raise it to 2026.7.11 — the first *installable* release that recognizes `monorepo_root`. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
scottschreckengaust
changed the title
scottschreckengaust
marked this pull request as ready for review
September 14, 2026 19:36
ayushtr-aws
approved these changes
Sep 14, 2026
scottschreckengaust
enabled auto-merge
September 14, 2026 20:28
isadeks
approved these changes
Sep 14, 2026
scottschreckengaust
deleted the
fix/887-mise-min-version-monorepo-root
branch
September 14, 2026 22:00
4 tasks
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
3 participants
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.
Raise the mise
min_versionfloor so the committedmonorepo_rootkey parses without warning.Area
tooling— rootmise.toml, scripts, CI workflowsRelated
Closes #887. Follow-up to #874 (which renamed
experimental_monorepo_root→monorepo_root). Key introduced by jdx/mise#11052.Changes
min_version2026.2.6→2026.7.11across all five mise configs — rootmise.toml(the one that carriesmonorepo_root) plus the four workspace configscdk/,agent/,cli/,docs/, which share the same floor by design and are kept uniform.Why: #874 renamed the monorepo key to
monorepo_root, but that key did not exist until the 2026.7.9 tag (changelog## [2026.7.9] - 2026-07-16, PR jdx/mise#11052 "deprecate experimental monorepo root key"). The old floor2026.2.6therefore no longer matches the config the repo requires: any contributor on2026.2.6 ≤ mise < 2026.7.11gets, on every shell prompt / task run:Raising the floor turns that silent per-prompt warning into a clear "please upgrade mise" gate.
Why 2026.7.11 and not 2026.7.9? The key first appears in the
2026.7.9tag, but2026.7.8,2026.7.9, and2026.7.10were tagged and never published to the install/release channels (a release-pipeline issue upstream); their changes shipped in 2026.7.11 (published 2026-07-20). Pinning the floor to2026.7.9would trade a warning for an unsatisfiable requirement —mise use 2026.7.9can't install a version that was never released.2026.7.11is the first installable release that recognizesmonorepo_root, so it is the correct floor.Note: validation is trust-gated
mise only emits the unknown-field warning for trusted configs; an untrusted copy parses leniently and stays silent. The reproduction below runs against a trusted config so the warning surfaces deterministically.
Verification (BONUS: below-floor vs at-floor)
Same trusted config (
monorepo_root = true+[monorepo].config_roots), only the mise binary changes:2026.3.1) → emitsunknown field: monorepo_root.2026.7.11, checksum-verified) → clean.2026.7.11is used for the at-floor run precisely because it is the first published release carrying the key (2026.7.8–2026.7.10were tagged but never released; see "Why 2026.7.11" above).Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.
🤖 Generated with Claude Code