wp-plugin-releaselisted

# WordPress Plugin Release / Version Sync Bump a WP plugin version coherently. Prevents the classic drift where the plugin header says one version, the `readme.txt` `Stable tag` another, and the `.pot` a third. ## When to use - "Release X.Y.Z", "bump the version", "update the changelog / readme.txt". - After substantial work has landed under an unreleased version. ## First: determine the real current state ```bash git tag # any release tags? gh release list # any published releases? grep -n "Version:" *.php # plugin header grep -n "_VERSION'" *.php # version constant grep -n "Stable tag" readme.txt ``` If header/constant/Stable-tag disagree, that drift IS the problem — pick the target version and sync all of them. Choose the bump by semver: new backward-compatible features → minor; fixes only → patch; breaking → major. Internal-only refactors (dir rename) don't force a major. ## Sources to update (all, in lockstep) 1. **Plugin header** `* Version: X.Y.Z` (main plugin file). 2. **Version constant** `define( 'PLUGIN_VERSION', 'X.Y.Z' )`. 3. **`readme.txt` `Stable tag: X.Y.Z`** — and `Tested up to` / `Requires PHP` if they changed. 4. **`readme.txt` Changelog** — add a `= X.Y.Z =` block listing what shipped (security, features, fixes), grouped. 5. **`readme.txt` Upgrade Notice** — add `= X.Y.Z =` one-liner (why upgrade). 6. **`.pot`** — regenerate so `Project-Id-Version` matches and new strings are captured: ```bash c