Update ajv: 6.9.1 → 6.10.2 (minor)
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ ajv (6.9.1 → 6.10.2) · Repo
Release Notes
6.10.2
Fix: the unknown keywords were ignored with the option
strictKeywords: true(instead of failing compilation) in some sub-schemas (e.g. anyOf), when the sub-schema didn't have known keywords.
6.10.0
Option
strictDefaultsto report ignored defaults (#957, @not-an-aardvark)
OptionstrictKeywordsto report unknown keywords (#781)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 39 commits:
6.10.2fix: the unknown keyword in the schema without known keywords inside compound schema (e.g. anyOf) is ignored with strictKeywords optionreadme: fix linkTidelift subscriptionsecurity contactCreate FUNDING.ymllabels configlabel comments (for labelcious)6.10.1chore(package): update del-cli to version 2.0.0 (#1014)chore(package): update eslint to version 6.0.0 (#1030)test: update node.js versions for travis testchore: update jshintchore(package): update nyc to version 14.0.0 (#994)Add "empty" to useDefaults Option type definition (#1020)fix: addKeyword and schema without ID, closes #1001chore(package): update karma to version 4.0.1 (#959)fix(types): add strictKeywords to Options interface (#975)update JSON-Schema-Test-SuiteFix wrong json schema reference (#961)6.10.0refactor: strictDefaults optionfeat: strictKeywords option to report unknown keywords, closes #781style: fixadditional tests for strictDefault optionsMerge branch 'not-an-aardvark-invalidDefaults-option'rename option to strictDefaultsfeat: invalidDefaults option to warn when defaults are ignored, fixes #9576.9.2chore(package): update mocha to version 6.0.0 (#952)feat: extract method to validate custom keyword definitionfix: removeAdditional option breaking custom keywords, closes #955, closes epoberezkin/ajv-keywords#91Replace single quotes with double quotes to get build scripts running on Windows (#946)update package.json scriptstest: enable browser tests in node 10skip browser testsrefactor: split issues.spec.js filerefactor: split options.spec.js filechore(package): update nyc to version 13.2.0 (#930)
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.
All Depfu comment commands
- @depfu rebase
- Rebases against your default branch and redoes this update
- @depfu merge
- Merges this PR once your tests are passing and conflicts are resolved
- @depfu close
- Closes this PR and deletes the branch
- @depfu reopen
- Restores the branch and reopens this PR (if it's closed)
- @depfu pause
- Ignores all future updates for this dependency and closes this PR
- @depfu pause [minor|major]
- Ignores all future minor/major updates for this dependency and closes this PR
- @depfu resume
- Future versions of this dependency will create PRs again (leaves this PR as is)