Repository navigation
fix(cli): use exact compiler policy in init plans - #200
Merged
Merged
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
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.
Closes #199.
Replace the duplicated TypeScript range in init planning with TYPESCRIPT_COMPILER_SUPPORT_POLICY.exactVersion from the existing stable compiler dependency. The compiler rejects untested patches, so generated dependency proposals must not float to them. Existing user dependency ranges are still preserved.
Adds a policy-backed assertion for every built-in grammar and a patch Changeset. Focused planner tests and formatting pass. Required CI gates merging.