The version of ESLint you are using.

7.14

The problem you want to solve.

Migrate eslint to Ajv version 7 at the time it is released in December as the main version, to ensure that the users migrating to Ajv v7 and using eslint (that depends on Ajv version 6) do not have any version conflicts.

Your take on the correct solution to problem.

Upgrade in eslint:

• Ajv and other related dependencies versions (e.g. ajv-keywords)
• any Ajv API/options changes
• JSON Schema to draft-07 - Ajv v7 removed support for draft-04 (which is 4 versions old), the change logs are here: https://github.com/ajv-validator/ajv/releases

My concern that any plugins that rely on JSON Schema draft-04 specific features may need to be upgraded too, but nothing has been reported so far; although not too many users started using Ajv v7 beta, it is growing judging by ajv-formats downloads that was split from Ajv in v7: https://www.npmjs.com/package/ajv-formats

Either way, it most likely should be a major version change in eslint too to avoid any issues for the users - do you agree?

I am planning a release candidate version 7.0.0-rc.0 some time next week, and the main version release within a couple of weeks this year; I think I should make a PR to eslint once 7.0.0-rc.0 is released.

Let me know if you have any concerns / comments / questions

Are you willing to submit a pull request to implement this change?

Yes