fix(deps): update dependency ajv to v6.12.3 [security] - autoclosed #72
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.
This PR contains the following updates:
6.3.0
->6.12.3
GitHub Vulnerability Alerts
CVE-2020-15366
An issue was discovered in ajv.validate() in Ajv (aka Another JSON Schema Validator) 6.12.2. A carefully crafted JSON schema could be provided that allows execution of other code by prototype pollution. (While untrusted schemas are recommended against, the worst case of an untrusted schema should be a denial of service, not execution of code.)
Release Notes
ajv-validator/ajv (ajv)
v6.12.3
Compare Source
Pass schema object to processCode function
Option for strictNumbers (@issacgerges, #1128)
Fixed vulnerability related to untrusted schemas (CVE-2020-15366)
v6.12.2
Compare Source
Removed post-install script
v6.12.1
Compare Source
Docs and dependency updates
v6.12.0
Compare Source
Improved hostname validation (@sambauers, #1143)
Option
keywords
to add custom keywords (@franciscomorais, #1137)Types fixes (@boenrobot, @MattiAstedrone)
Docs:
v6.11.0
Compare Source
Time formats support two digit and colon-less variants of timezone offset (#1061 , @cjpillsbury)
Docs: RegExp related security considerations
Tests: Disabled failing typescript test
v6.10.2
Compare Source
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.v6.10.1
Compare Source
Fix types
Fix addSchema (#1001)
Update dependencies
v6.10.0
Compare Source
Option
strictDefaults
to report ignored defaults (#957, @not-an-aardvark)Option
strictKeywords
to report unknown keywords (#781)v6.9.2
Compare Source
v6.9.1
Compare Source
v6.9.0
Compare Source
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.v6.8.1
Compare Source
v6.8.0
Compare Source
Docs: security considerations.
Meta-schema for the security assessment of JSON Schemas.
v6.7.0
Compare Source
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.
v6.6.2
Compare Source
v6.6.1
Compare Source
v6.6.0
Compare Source
Keyword "nullable" from OpenAPI spec
Replaced phantomjs with headless chrome
v6.5.5
Compare Source
v6.5.4
Compare Source
v6.5.3
Compare Source
v6.5.2
Compare Source
v6.5.1
Compare Source
v6.5.0
Compare Source
With option
passContext
, the context is now passed in recursive/mutually recursive refs (@cvlab, #768).v6.4.0
Compare Source
Support URNs in $id - core
url
package is replaced withurl-js
(#423, @sondrele).Configuration
📅 Schedule: Branch creation - "" in timezone America/New_York, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.