JLHwung / postcss-font-family-system-ui

PostCSS plugin to transform W3C CSS font-family: system-ui to a practical font-family list
Creative Commons Zero v1.0 Universal
94 stars 8 forks source link

chore(deps): update dependency ajv to v7.2.4 #412

Closed renovate[bot] closed 1 year ago

renovate[bot] commented 3 years ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
ajv (source) 7.0.4 -> 7.2.4 age adoption passing confidence

Release Notes

ajv-validator/ajv ### [`v7.2.4`](https://togithub.com/ajv-validator/ajv/releases/tag/v7.2.4) [Compare Source](https://togithub.com/ajv-validator/ajv/compare/v7.2.3...v7.2.4) Fix [#​1515](https://togithub.com/ajv-validator/ajv/issues/1515): correctly initialize evaluated properties. ### [`v7.2.3`](https://togithub.com/ajv-validator/ajv/releases/tag/v7.2.3) [Compare Source](https://togithub.com/ajv-validator/ajv/compare/v7.2.2...v7.2.3) Remove docs from npm package ### [`v7.2.2`](https://togithub.com/ajv-validator/ajv/releases/tag/v7.2.2) [Compare Source](https://togithub.com/ajv-validator/ajv/compare/v7.2.1...v7.2.2) Docs correction Simplified JSONSchemaType ([@​erikbrinkman](https://togithub.com/erikbrinkman)) Fix [#​1493](https://togithub.com/ajv-validator/ajv/issues/1493) - incorrect reporting of missing required property with option `ownProperties: true` Fix [#​1501](https://togithub.com/ajv-validator/ajv/issues/1501) - JTD not working correctly with many properties in the schema ### [`v7.2.1`](https://togithub.com/ajv-validator/ajv/releases/tag/v7.2.1) [Compare Source](https://togithub.com/ajv-validator/ajv/compare/v7.2.0...v7.2.1) Add [tests](https://togithub.com/nst/JSONTestSuite) and fix parsers compiled with `ajv.compileParser` from JTD schemas: - fail on invalid JSON: - trailing comma in arrays/objects - invalid JSON numbers - control characters in strings - fix parsing of u-escaped characters - do not fail on duplicate object keys (consistent with JSON.parse) Compiled parsers are now: - consistent with JSON.parse in case of invalid JSON - only parse data that is valid for JTD schema It is a breaking change for compiled parsers compared with 7.2.0 that was released earlier on the same day. ### [`v7.2.0`](https://togithub.com/ajv-validator/ajv/releases/tag/v7.2.0) [Compare Source](https://togithub.com/ajv-validator/ajv/compare/v7.1.1...v7.2.0) strictRequired option (off by default) - to log or fail if properties used in JSON Schema "required" are not defined in "properties" ([@​PBug90](https://togithub.com/PBug90), [#​1403](https://togithub.com/ajv-validator/ajv/issues/1403)) Compiled parsers (as fast as JSON.parse on valid JSON, but replace validation and fail much faster on invalid JSON) and serializers (10x+ faster than JSON.stringify) from JSON Type Definition schemas ([#​1454](https://togithub.com/ajv-validator/ajv/issues/1454)) - see examples in [javascript](https://ajv.js.org/guide/getting-started.html#parsing-and-serializing-json) and [typescript](https://ajv.js.org/guide/typescript.html#type-safe-parsers-and-serializers) Please note: there are fixes to compiled parsers in [7.2.1](https://togithub.com/ajv-validator/ajv/releases/tag/v7.2.1) The website migrated to VuePress and documentation is restructured to make navigating Ajv documentation and learning easier - this is still work in progress, but already some improvement on the information structure. Any feedback/corrections would be very much appreciated! Improved TypeScript support for JSONSchemaType: - JTDSchemaType utility type to convert your data type into the type of JTD schema, to simplify its writing and to make sure it is consistent with your data type, with type inference support for ajv methods ([@​erikbrinkman](https://togithub.com/erikbrinkman), [#​1446](https://togithub.com/ajv-validator/ajv/issues/1446), [#​1456](https://togithub.com/ajv-validator/ajv/issues/1456), [#​1457](https://togithub.com/ajv-validator/ajv/issues/1457), [#​1475](https://togithub.com/ajv-validator/ajv/issues/1475)) - see [example here](https://ajv.js.org/guide/typescript.html#utility-types-for-schemas) - Alternatively, you can use JTDDataType utility type to convert your JTD schema type into the type of data ([@​erikbrinkman](https://togithub.com/erikbrinkman), [#​1458](https://togithub.com/ajv-validator/ajv/issues/1458)) - see [this example](https://ajv.js.org/guide/typescript.html#utility-type-for-jtd-data-type) Other improvements by [@​Fdawgs](https://togithub.com/Fdawgs) ([#​1466](https://togithub.com/ajv-validator/ajv/issues/1466)), [@​t7yang](https://togithub.com/t7yang) ([#​1472](https://togithub.com/ajv-validator/ajv/issues/1472), [#​1473](https://togithub.com/ajv-validator/ajv/issues/1473)), [@​koba04](https://togithub.com/koba04) ([#​1460](https://togithub.com/ajv-validator/ajv/issues/1460)) ### [`v7.1.1`](https://togithub.com/ajv-validator/ajv/releases/tag/v7.1.1) [Compare Source](https://togithub.com/ajv-validator/ajv/compare/v7.1.0...v7.1.1) Support readonly arrays with JSONSchemaType ([@​LinusU](https://togithub.com/LinusU), [#​1447](https://togithub.com/ajv-validator/ajv/issues/1447)) ### [`v7.1.0`](https://togithub.com/ajv-validator/ajv/releases/tag/v7.1.0) [Compare Source](https://togithub.com/ajv-validator/ajv/compare/v7.0.4...v7.1.0) Support for JSON Type Definition RFC 8927 - a simple schema language provided as an alternative to JSON Schema. See these docs: - an [informal document](https://ajv.js.org/json-type-definition.html) on Ajv site - [RFC8927](https://datatracker.ietf.org/doc/rfc8927/) - [choosing schema language](https://ajv.js.org/guide/schema-language.html) - comparison with JSON Schema Allow ":" in keyword names ([#​1421](https://togithub.com/ajv-validator/ajv/issues/1421), [@​teq0](https://togithub.com/teq0))

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, 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.

renovate[bot] commented 1 year ago

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

Warning: custom changes will be lost.