-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An in-range update of ajv is breaking the build 🚨 #3
Comments
Version 5.1.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 5.1.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 13 commits.
See the full diff |
Version 5.1.3 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 5.1.4 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 7 commits.
See the full diff |
Version 5.1.6 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 10 commits.
See the full diff |
Version 5.2.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notes5.2.0Refactor: separate "equal" into package fast-deep-equal |
Version 5.2.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 13 commits.
See the full diff |
Version 5.2.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 5.2.3 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 11 commits.
See the full diff |
Version 5.2.4 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 23 commits.
There are 23 commits in total. See the full diff |
Version 5.2.5 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 5.3.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv5.3.0Replace json-stable-stringify with a faster fork without jsonify. |
Version 5.4.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv5.4.0Option CommitsThe new version differs by 20 commits.
There are 20 commits in total. See the full diff |
Version 5.5.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 8 commits.
See the full diff |
Version 5.5.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 5.5.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 13 commits.
See the full diff |
Version 5.1.0 of ajv just got published.
This version is covered by your current version range and after updating it in your project the build failed.
ajv is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪
Status Details
Release Notes
v5.1.0Changed order of type validation - "type" keyword is now validated before keywords that apply to all types.
Commits
The new version differs by 7 commits0.
d2cb328
5.1.0
a8d91c5
Merge pull request #488 from epoberezkin/type-validation
a02b9a6
refactor: make sure "type": "integer" is vaildated before other keywords, closes #485
f60fedb
feat: validate types before other keywords, #485
6f0ff64
docs: fix example for additionalProperties keyword
78fffde
Merge pull request #479 from handrews/error-doc
a71cece
docs: FAQ for additionalProperties error messages
false
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
The text was updated successfully, but these errors were encountered: