chore: sibling constraints declare a requirement, not a history - #13
Merged
Conversation
This manifest enumerated one minor per release of its siblings, so every minor bump anywhere in the family cost a widening pull request here. That ceiling was protecting nothing: the answer to it firing was always to widen it, and a gate opened every time it rings is paperwork. The range asserts that Milpa's 0.x minors are compatible with each other — a claim about this family's discipline, and one this repo's own suite is what actually verifies. The floor is kept exactly where the enumeration had it, so nothing older is admitted than before. Greenhouse decisions/0034.
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.
Collapses 1 enumerated sibling constraint(s) into ranges. The floor stays where the enumeration had it.
Greenhouse
decisions/0034: a gate whose answer to firing was always to widen it was not protecting anything, and each consumer's suite is what actually verified compatibility.