Changelog
What changed in each release.
2.0.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)
2.0.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)
2.0.0 (2026-10-29)
- Add monorepo support with a workspace release model. One release plan now covers every package discovered from configured package groups (glob, exclude, fixed
idor identifier source, and per-group version targets), changeset frontmatter lists multiple packages with their bumps,statusandversion --dry-run --jsonemit the per-packagereleases[]shape, andaddprompts for affected packages or takes repeatable--package NAME|PATHwith one--bumpfor all or one per package. Configuration moves to a PHP-first root file,changesets.config.php, built with thedefine_config()function, namespaced descriptor builders and thenextVersionandchangelogEntryhooks, and version callbacks are available in every config path. Tags default to{path}/{version}like wp-release, while an inferred root project keepsv{version}. A newtagscommand lists the tags that released versions still need, with their changelog notes,status,versionandtagstake--github-outputfor GitHub Actions step outputs, and the README shows a release workflow that combines them with a pull request action andgh release.readmeChangelogadds release sections to the== Changelog ==of a plugin readme. A root package is never named after the checkout directory: inference names a plugin by its main file slug, and a configured root package needs anidor a manifest name. Versions may have two to four parts, like the2.1and1.2.3.4versions common in WordPress plugins. Pre-releases are supported statelessly:version --prerelease <id>turns the stable plan into pre-release versions numbered from the package git tags, also for hooked versions, a later stable release graduates the pre-release likesemver inc, and the WordPress readme stable tag keeps the last stable version. Breaking changes: the former.php-changesets.json,.changeset/config.phpandconfig/changesets.phpformats are removed, the new config file changes the project schema, the default tag format changes, and the CLI JSON output is lists of releases. (3cc9bb3) - Follow the wp-release CLI conventions. The executable is now
changeset, likevendor/bin/changeset add, and itsadd,status,versionandtagcommands take the options of the wp-releasechangeset-*commands.tagcreates the missing release tags, checks the version targets first and pushes them one at a time with--push, and lists them with--dry-runor--untagged, with--since,--package,--versionand--release-title(or thereleaseTitlesetting); each tag reports its title, previous tag, status and release notes, from the changelog or else the commits since the previous tag.version --packageversions only some packages andversion --snapshot <id>releases timestamped snapshots. TheremoteandbaseBranchsettings, with--remoteand--base-branch, set the default comparison ofstatusandadd.status --since <ref>fails with exit code 2 for each changed package without a changeset added since the ref, andadd --since <ref>releases those packages. Every command takes--jsonand--github-output,--log-format github(or--ci, the default in GitHub Actions) reports errors as annotations on their files and lines and adds job summaries, and the global--config,--tag-formatand--project-nameoptions work like in wp-release. Exit codes follow wp-release: 1 for unexpected failures like a failed git command and 2 for validation errors. Breaking changes: thechangesetsexecutable is renamed tochangeset, thetagscommand is replaced bytag, which creates the tags (usetag --untaggedto only list them),readmeChangelogis opt-in and no longer inferred from the readme, and releases carry achangelogMarkdown list instead of thenotesarray. The documentation moves to the packagedocs/directory, with GitHub Actions workflows for the pull request check, release pull requests and GitHub releases. (486b4aa)
1.0.0 (2026-10-29)
- Align coding style with the monorepo, use snake_case public APIs, and replace static project utilities with injected project-bound services. (
aa18298)
0.1.1 (2026-10-29)
- Document the package release repository after its first tagged release. (
baa3b0f)