comit-network / comit-rs

Reference implementation of COMIT, an open protocol facilitating trustless cross-blockchain applications.
GNU General Public License v3.0
191 stars 33 forks source link

Bump ajv from 6.12.6 to 7.1.0 in /tests #3501

Closed dependabot[bot] closed 3 years ago

dependabot[bot] commented 3 years ago

Bumps ajv from 6.12.6 to 7.1.0.

Release notes

Sourced from ajv's releases.

v7.1.0

Support for JSON Type Definition RFC 8927 - a simple schema language provided as an alternative to JSON Schema.

See these docs:

Allow ":" in keyword names (#1421, @teq0)

v7.0.4

Fix: duplicate functions in standalone validation code with mutually recursive schemas (#1361) Fix: reference resolution when base URI change was not applied (#1414)

v7.0.3

Fixes:

  • oneOf error type (#1368, @G-Rath)
  • remove multiple imports (rollup/plugins#745)

Docs:

  • Using in ES5 (#1364, @aladdin-add)
  • Option strictTypes: false has to be used with json-schema-secure schema (#1373)

v7.0.2

Remove duplicate functions from standalone validation code (#1361)

v7.0.1

Update error message for maxLength/minLength keywords

v7.0.0

Please note: this document covers the changes from v6.12.6.

The main changes

  • support of JSON Schema draft-2019-09 features: unevaluatedProperties and unevaluatedItems, dynamic recursive references and other additional keywords.
  • comprehensive support for standalone validation code - compiling one or multiple schemas to standalone modules with one or multiple exports.
  • to reduce the mistakes in JSON schemas and unexpected validation results, strict mode is added - it prohibits ignored or ambiguous JSON Schema elements. See Strict mode and Options for more details
  • to make code injection from untrusted schemas impossible, code generation is fully re-written to be type-level safe against code injection.
  • to simplify Ajv extensions, the new keyword API that is used by pre-defined keywords is available to user-defined keywords - it is much easier to define any keywords now, especially with subschemas.
  • schemas are compiled to ES6 code (ES5 code generation is supported with an option).
  • to improve reliability and maintainability the code is migrated to TypeScript.
  • separate Ajv classes from draft-07 and draft-2019-09 support with different default imports (see Getting started or v7.0.0-beta.5 for the details).

Please note:

  • the support for JSON-Schema draft-04 is removed - if you have schemas using "id" attributes you have to replace them with "$id" (or continue using version 6 that will be supported until 02/28/2021).
  • all formats are separated to ajv-formats package - they have to be explicitly added if you use them.
  • Ajv instance can only be created with new keyword, as Ajv is now ES6 class.
  • browser bundles are automatically published to ajv-dist package (but still available on cdnjs.com).
  • order of schema keyword validation changed - keywords that apply to all types (allOf etc.) are now validated first, before the keywords that apply to specific data types. You can still define custom keywords that apply to all types AND are validated after type-specific keywords using option post: true in keyword definition.
  • regular expressions in keywords "pattern" and "patternProperties" are now used as if they had unicode "u" flag, as required by JSON Schema specification - it means that some regular expressions that were valid with Ajv v6 are now invalid (and vice versa).

... (truncated)

Commits
  • 8ec80c4 7.1.0
  • 60dd7ae Merge pull request #1438 from ajv-validator/dependabot/npm_and_yarn/husky-5.0.9
  • 9af75b5 build(deps-dev): bump husky from 4.3.8 to 5.0.9
  • 1996f6b Merge pull request #1428 from ajv-validator/jtd
  • 078d6a8 note on JTD error objects
  • 9e5f247 JTD: improve error reporting, remove extra error for properties
  • d6acee4 add optional instancePath property to error object
  • 7e1711e JTD options, support inlineRefs option, fix removeAdditional option
  • 4a9084a jtd error format
  • 5ddef2e JTD docs
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
mergify[bot] commented 3 years ago

bors r+

bors[bot] commented 3 years ago

Build failed (retrying...):

bors[bot] commented 3 years ago

Build failed:

dependabot[bot] commented 3 years ago

Superseded by #3508.