Reach milpa/command ^0.7 - #16
Merged
Merged
Conversation
…imension The effect ceiling gained an axis that answers what a change is made OF rather than how much of it there is, and this package's constraint kept the resolver on the previous major even for apps that asked for the new one. Measured before widening: swapping the new atom into an app built against the old constraint left the suite bit-identical — same tests, same assertions, same skips — so the cap was conservative rather than protective. Suite green on the new range.
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.
The effect ceiling grew a fifth dimension — what a change is made OF, not how much of it there is — and this package's constraint kept the resolver on the previous major even for apps that asked for the new one.
Measured before widening (greenhouse
evidence/0133): swapping the new atom into an app built against the old constraint left the suite bit-identical — same tests, same assertions, same skips — so the cap was conservative rather than protective.Suite green on the new range.