Changelog
What changed in each release.
0.2.2 (2026-11-15)
- Start each documentation page with a
# Titleheading instead of atitlein the front matter, so that the Markdown pages read well on GitHub and innode_modules. (ca287e4) - Move the detailed usage documentation from the README into topic pages of the
docs/directory, and publish it in the npm package, so that the docs site has a guide for each area and agents and editors can read the documentation of the installed version. (ca287e4) - Point the package homepage to the documentation site, so that the Homepage link on the npm package page works without access to the private repository. (
ca287e4)
0.2.1 (2026-11-11)
- Group the wp-release commands as
changeset add|status|version|tag,deploy svn|gitandi18n pot|audit|mo|json|php, and runchangeset addfor a barewp-release changeset, so that a"changeset": "wp-release changeset"script runsnpm run changeset. The dashed names likechangeset-addkeep working as aliases, andexecute()andCommandResultsuse the grouped names. (0bb0b18)
0.2.0 (2026-10-31)
- Choose how POT entries name their source with
--add-location <full|file|never>and--no-location, orlocationin the i18n configuration.filewrites#: path/to/file.phpwithout the line number, so that editing a source file does not change the POT unless its strings change.--no-referencesandreferences: falsekeep working and meannever. (9a7a89b)
0.1.0 (2026-10-29)
- Add the gettext library extracted from wp-release: extract translatable strings from PHP, JavaScript and block.json sources into POT catalogs, compile PO files to MO, JED JSON and
.l10n.php, and audit catalogs, with a sub-path export per feature and plugin or theme headers passed in as input. (16bf135)