CodeCharter ships new versions regularly. The Downloads page always shows the current version together with its release notes, plus a list of the most recent earlier releases with their own notes. This wiki page deliberately does not repeat that list — it changes far more often than the documentation, and a copy here would drift out of sync with the version you are actually running.
How release notes are organized
Release notes follow the Keep a Changelog convention: within one release, entries are grouped under headings such as Added (new commands, options, rule-authoring capabilities, or built-in rules), Changed (behavior that shifted without breaking existing usage), Removed (a breaking change — only appears in a major-version release), Fixed (bug fixes), and Security, whichever apply to that release.
Checking what changed since your last upgrade
Run codecharter --version to see exactly which build you have (see
Versioning for how to read the output), then
open that version's notes on the Downloads page and read forward through
every release up to the one you are moving to. The SemVer contract described
on the Versioning page tells you in advance which kind of change to expect
at each version level: a patch or minor upgrade is always safe to take
without review, a major upgrade is the one worth reading closely.