Version 2.2.2

What's Changed

• Improved validation and robustness
• Loading possible readme locations in parallel, slightly speeding up the action.

Full Changelog: v2.2.1...v2.2.2

Version 2.2.1

What's Changed

• Updated GitHub API libraries

Full Changelog: v2.2.0...v2.2.1

Version 2.2.0

What's Changed

• Running on Node 20

Full Changelog: v2.1.0...v2.2.0

v2.1.0

What's Changed

• Fixed parsing of readmes with trailing whitespace
• Added src/readme.txt and readmes with .md extension to defaults

New Contributors

• @jdevalk made their first contribution in #1104

Full Changelog: v2.0.0...v2.1.0

Version 2.0.0

BREAKING CHANGES

• The default WordPress update channel is now "RC". To keep the original behaviour, set channel: "stable" in your .wordpress-version-checker.json

Full Changelog: v1.5.1...v2.0.0

Version 1.5.1

What's Changed

• Fixed parsing of readmes with Windows linebreaks

Full Changelog: v1.5.0...v1.5.1

Version 1.5.0

What's Changed

• Enabled support for the beta channel by @marekdedic in #915

Full Changelog: v1.4.2...v1.5.0

Version 1.4.2

What's Changed

• Fixed errors with WordPress version parsing which were caused by a change to how WordPress reports its versions

Full Changelog: v1.4.1...v1.4.2

Version 1.4.1

What's Changed

• Fixed parsing of readme with multiple spaces after :

Full Changelog: v1.4.0...v1.4.1

Version 1.4.0

New functionality:

• Added the option to start reporting an upcoming WordPress version even before its release, when it reaches the "Release Candidate" phase.
  • In an upcoming release, it will also be possible to start reporting when the first beta versions are released
  • The default value will change to start reporting in the "Release candidate" phase in version 2.0.0
  • More details in the readme
• The config readme field can now be an array of paths to scan for the readme file.
• All config fields are now optional

Minor changes:

• More resilient error reporting on invalid config