Skip to content

Sync 0.5.0 release back into develop - #34

Merged
GaryJones merged 5 commits into
developfrom
main
Aug 20, 2026
Merged

Sync 0.5.0 release back into develop#34
GaryJones merged 5 commits into
developfrom
main

Conversation

@GaryJones

Copy link
Copy Markdown
Contributor

Summary

Completes the git-flow cycle for the 0.5.0 release by merging main back into develop. The release was prepared on a branch off develop and merged into main (#32), where 0.5.0 was tagged; this brings those release commits back so develop is not left behind main.

The commits carried across are the release housekeeping only: the expanded changelog, the generated translation template (languages/safe-report-comments.pot), the version bump to 0.5.0, and the new i18n Composer script. No functional code differs between the branches.

Releases require a refreshed translation template, but the project had
no repeatable way to produce one. Add an `i18n` Composer script wrapping
`wp i18n make-pot`, pinning `--slug` and `--domain` to the plugin so the
generated headers (such as `Report-Msgid-Bugs-To`) never fall back to
the working directory's name, which in a Conductor worktree is not the
plugin slug.
@GaryJones
GaryJones merged commit 5a4ef64 into develop Aug 20, 2026
10 checks passed
@GaryJones
GaryJones deleted the main branch August 20, 2026 01:09
@GaryJones GaryJones added this to the 0.5.0 milestone Aug 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant