fix(tooling): migrate deprecated mise monorepo setting - #874
Merged
Merged
Conversation
scottschreckengaust
enabled auto-merge
September 10, 2026 14:22
isadeks
approved these changes
Sep 10, 2026
This was referenced Sep 14, 2026
Closed
ClintEastman02
pushed a commit
to ClintEastman02/sample-autonomous-cloud-coding-agents
that referenced
this pull request
Sep 15, 2026
…t key (aws-samples#888) * fix(tooling): bump mise min_version to 2026.7.9 for the monorepo_root key PR aws-samples#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 aws-samples#887 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(tooling): raise child mise.toml floors to 2026.7.9 for consistency 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 aws-samples#887 * fix(tooling): correct floor to 2026.7.11 — 2026.7.8–2026.7.10 were never 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> --------- Co-authored-by: scottschreckengaust <345885+scottschreckengaust@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com> Co-authored-by: ayushtr-aws <ayushtr@amazon.com>
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.
The reported
security:depsfailure was fixed onmainby #870, which upgradedsmol-tomlfrom 1.7.0 to 1.8.0. This PR addresses the remaining warning in the same CI output by migrating mise's deprecated monorepo root setting before its scheduled removal.Area
cdk— infrastructure, handlers, constructsagent— Python runtime / Docker imagecli—bgagentclientdocs— guides or design sources (docs/guides/,docs/design/)tooling— rootmise.toml, scripts, CI workflowsRelated
Changes
experimental_monorepo_root = truewithmonorepo_root = trueVerification
MISE_EXPERIMENTAL=1 mise tasks --all— 75 tasks discovered, no deprecation warningmise run security:deps— No issues found, no deprecation warningmise run build— passedmise run installinstalled dependencies, then hit the documented localcore.hooksPathconflict at the finalprek installstepAcknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.