[Snyk] Upgrade ajv from 6.5.3 to 6.10.2 #3
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.
Snyk has created this PR to upgrade
ajv
from 6.5.3 to 6.10.2.Release notes
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.Fix types
Fix addSchema (#1001)
Update dependencies
Option
strictDefaults
to report ignored defaults (#957, @not-an-aardvark)Option
strictKeywords
to report unknown keywords (#781)6.9.2
6.9.1
OpenAPI keyword
nullable
can be any boolean (and not onlytrue
).Custom keyword definition changes:
dependencies
option in to require the presence of keywords in the same schema.6.8.1
Docs: security considerations.
Meta-schema for the security assessment of JSON Schemas.
Option
useDefaults: "empty"
to replacenull
and""
(empty strings) with default values (in addition to assigning defaults to missing and undefined properties).Update draft-04 meta-schema to remove incorrect usage of "uri" format.
6.6.2
from
ajv
GitHub Release Notes🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs