prepare-changelog-release

To automate changelog updates for a WordPress plugin release, you run a process that reads the plugin version from the main file header and rewrites the Unreleased block in CHANGELOG.md with that version and date.

An Unreleased section in a changelog is used to collect new changes before a versioned release. During release workflows, the current version and date are inserted into this block, and a fresh empty Unreleased section is created at the top for future entries.

A release workflow reads the current version from a WordPress plugin by parsing the main plugin file header. It uses this extracted version number to update the CHANGELOG.md file during the automated release process.

This changelog automation is specifically built for WordPress plugin release workflows and relies on reading the version from the main plugin file header. Using it for non-WordPress projects is not supported unless they follow the exact same plugin header format.

The best way to maintain a consistent changelog format across plugin versions is to automate the process of moving the current version and date into the Unreleased section during releases, ensuring the CHANGELOG.md follows the project's required format.

Your changelog Unreleased section needs to be rewritten during a release to insert the current plugin version and date, creating a finalized entry for that release and establishing a fresh empty Unreleased block at the top for future development changes.