Major release plan for validator library

This is a quick overview of the next major releases that we have planned for the validator library. This is not an exthausive list, but should give interested people a general idea of our plans.

The idea is that we work in various phases per major release;

• We start with a feature freeze on all non-security PRs.
• We will then work on merging breaking changes for the next major release.
• After that work has completed and a new major release has been published, we will start work on the improvements and merging other PRs.
• Once we feel comfortable that we have introduced enough improvements, we will start the cycle again with a feature freeze.

When a new major release is released, there will be a period of 6 months in which we will deal with security vulnerabilites. After those 6 months the previous major releases are marked as deprecated on npm (and potentially other sites) and no further work will be done.

v14

BREAKING CHANGES

• Removing support for EOL Node versions
• Specifying support policy for Node, browsers, Deno, Bun and potentially other runtimes

Improvements during that version

• Improving test suite by including testing on browsers, Deno, Bun and potentially other runtimes
• Splitting tests to a file per validator
• Moving tests to TypeScript
• Updating dependencies to latest versions
• Introducing Dependabot/Renovate to manage dependencies
• Introducing Release Please/semantic-release/changesets to manage releases
• Deploying validator to jsr.io (the Deno package manager) under the @validatorjs organization (owned by @WikiRik)

v15

BREAKING CHANGES

• Migrating source code to TypeScript
• Potentially; moving to ESM only

Improvements during that version

• More uniformity in how we define locales #1266 (comment)
• Moving optional parameters to the options object #1874

v16

BREAKING CHANGES

• Removing deprecated functionality