chore: pin the validator to oold 2.2.0 - #197
Merged
Merged
Conversation
2.1.0 vendored the meta-schema only to 1.0.0-rc.5, so make validate resolved latest to a candidate. 2.2.0 vendors 1.0.0.
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.
make validateran against a validator whose newest vendored meta-schema was1.0.0-rc.5, solatestresolved to a candidate on the repository that had just released 1.0.0. oold 2.2.0 vendors the 1.0.0 meta (oold-python#172).Result unchanged: 76 passing checks, the same 19 of 47 machine-checkable rules without a fixture. The four meta-schema documents are byte-identical between rc.5 and 1.0.0, so no validation behaviour moved; this makes the pin honest about which release it checks against.