fix(tooling): migrate deprecated mise monorepo setting - #874
Open
ayushtr-aws wants to merge 1 commit into
Open
Conversation
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.
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.