Changelog

What changed in each release.

Open as Markdown

0.2.2 (2026-11-15)

  • Start each documentation page with a # Title heading instead of a title in the front matter, so that the Markdown pages read well on GitHub and in node_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|git and i18n pot|audit|mo|json|php, and run changeset add for a bare wp-release changeset, so that a "changeset": "wp-release changeset" script runs npm run changeset. The dashed names like changeset-add keep working as aliases, and execute() and CommandResults use 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, or location in the i18n configuration. file writes #: path/to/file.php without the line number, so that editing a source file does not change the POT unless its strings change. --no-references and references: false keep working and mean never. (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)