Use project version of ajv-cli in all validation tasks #589
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The "ajv-cli" command line tool is used for validating data files against their JSON schema. The tool is used to validate the project's npm package.json configuration file. In general, it is preferable (and for some schemas even mandatory) to use the latest version of ajv-cli. However, support for the "Draft-04" schema specification was dropped in ajv-cli version 4.0.0. So when working with JSON schemas that specify that draft, it is necessary to use ajv-cli 3.3.0, the last compatible version. Previously, the package.json schema specified the "Draft-04" specification. For this reason, the `npm:validate` task was configured to use ajv-cli@3.3.0. The package.json schema has now been updated to use the "Draft-07" schema specification. So the code for using ajv-cli@3.3.0 is removed from the task, and it will now instead use the standard project level version of ajv-cli.
The "ajv-cli" command line tool is used for validating data files against their JSON schema. The tool is used to validate the project's Dependabot and ESLint configuration files. In general, it is preferable (and for some schemas even mandatory) to use the modern versions of ajv-cli. However, support for the "Draft-04" schema specification was dropped in ajv-cli version 4.0.0. So when working with JSON schemas that specify that draft, it is necessary to use ajv-cli 3.3.0, the last compatible version. Previously, the Dependabot and ESLint schema specified the "Draft-04" specification. For this reason, the `dependabot:validate` and `eslint:validate` tasks were configured to use ajv-cli@3.3.0. The schemas have now been updated to use "Draft-07". So the code for using ajv-cli@3.3.0 is removed from these tasks, and they will now use the standard project level version of ajv-cli.
per1234
added
type: enhancement
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The ajv-cli command line tool is used for validating data files against their JSON schema. The tool is used to validate the project's Dependabot, ESLint, and npm configuration files.
In general, it is preferable (and for some schemas even mandatory) to use the modern versions of ajv-cli. However, support for the "Draft-04" schema specification was dropped in ajv-cli version 4.0.0. So when working with JSON schemas that specify that draft, it is necessary to use ajv-cli 3.3.0, the last compatible version.
Previously, the Dependabot, ESLint, and npm schemas specified the "Draft-04" specification. For this reason, the
dependabot:validate,eslint:validate, andnpm:validatetasks were configured to useajv-cli@3.3.0.The schemas have now been updated to use "Draft-07" (SchemaStore/schemastore@11e62f6). So the code for using
ajv-cli@3.3.0is removed from these tasks, and they will now use the standard project level version of ajv-cli.