Support tagging prepared releases

Author: renatobo

AGENTS.md

@@ -45,6 +45,7 @@ Guidance for coding agents and contributors working in this repository.
 - Packaging workflow is defined under `.github/workflows/`.
 - The `quality.yml` workflow is the release gate; keep its WordPress/PHP matrix and immutable action pins current.
 - `release.sh` is the only supported tag-creation path. Do not add an automatic stable-tag workflow.
+- `release.sh` supports both an in-script version bump and version metadata already committed through a release pull request.
 - Release zip expects plugin files at repo root, including `*.php`, `readme.txt`, and `LICENSE`.
 - Checked-in API specs live under `docs/` and should stay aligned with the plugin routes.
 - GitHub Releases must publish the matching checked-in notes file from `release-notes/<version>.md`.

release.sh

@@ -218,7 +218,11 @@ assert_versions_match
 
 stage_release_support_files
 git add -- "$NOTES_FILE"
-git commit -m "Bump version to $VERSION"
+if git diff --cached --quiet; then
+  echo "Version $VERSION metadata is already committed; creating the release tag from HEAD."
+else
+  git commit -m "Bump version to $VERSION"
+fi
 git tag -a "$TAG" -m "Release $VERSION"
 git push origin main
 git push origin "$TAG"