Release tooling: plugin tags not pushed, and info.json changelog goes stale

[josephfusco]

Two defects in the plugin release pipeline. Neither blocks a release, but both need manual intervention today.

1. git push origin --tags pushes nothing

changeset publish in .github/workflows/npm-publish.yml logs New tag: @faustwp/wordpress-plugin@<v>. The next step, git push origin --tags, then reports Everything up-to-date. The tags never reach origin. release-plugin.yml triggers on those tags, so the wordpress.org deploy silently never fires.

Observed on 1.8.12. The tag had to be created and pushed by hand to trigger the deploy.

• The tags exist in the changesets output but not on origin.
• The Create GitHub Releases step (git tag --points-at HEAD) also finds nothing.
• Root cause: the pushed tags are not present in the working tree at push time. Needs investigation in the publish job step ordering.

Acceptance

• After a Version Packages merge, @faustwp/wordpress-plugin@<v> lands on origin automatically.
• release-plugin.yml triggers without a manual tag push.

2. info.json changelog never updates

.github/scripts/add-wpe-version-info-file.sh fetches the previously published info.json, then patches only versions, version, last_updated, download_link, tested, requires, and requires_php. It never rewrites sections.changelog.

So the changelog is inherited unchanged every release. It is currently frozen at 1.8.4. Users on the internal update channel do not see recent entries, including security fixes.

readme.txt already holds the current changelog (it has = 1.8.12 =). The script already reads other fields from readme.txt.

Acceptance

• sections.changelog in the generated info.json reflects the current readme.txt changelog.
• New releases show their own entry.