# Changelog

What changed in each release.

## 2.0.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`](https://github.com/wpelevator/basement/commit/ca287e459833429482d3e033eb3eab81eaea3757))

## 2.0.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`](https://github.com/wpelevator/basement/commit/0bb0b187cc93d3dd1ea9378764e00ef0a7a32f87))

## 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 `id` or identifier source, and per-group version targets), changeset frontmatter lists multiple packages with their bumps, `status` and `version --dry-run --json` emit the per-package `releases[]` shape, and `add` prompts for affected packages or takes repeatable `--package NAME|PATH` with one `--bump` for all or one per package. Configuration moves to a PHP-first root file, `changesets.config.php`, built with the `define_config()` function, namespaced descriptor builders and the `nextVersion` and `changelogEntry` hooks, and version callbacks are available in every config path. Tags default to `{path}/{version}` like wp-release, while an inferred root project keeps `v{version}`. A new `tags` command lists the tags that released versions still need, with their changelog notes, `status`, `version` and `tags` take `--github-output` for GitHub Actions step outputs, and the README shows a release workflow that combines them with a pull request action and `gh release`. `readmeChangelog` adds 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 an `id` or a manifest name. Versions may have two to four parts, like the `2.1` and `1.2.3.4` versions 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 like `semver inc`, and the WordPress readme stable tag keeps the last stable version. Breaking changes: the former `.php-changesets.json`, `.changeset/config.php` and `config/changesets.php` formats 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`](https://github.com/wpelevator/basement/commit/3cc9bb326760958c4e305551d3cfd0b5525ac2ca))
- Follow the wp-release CLI conventions. The executable is now `changeset`, like `vendor/bin/changeset add`, and its `add`, `status`, `version` and `tag` commands take the options of the wp-release `changeset-*` commands. `tag` creates the missing release tags, checks the version targets first and pushes them one at a time with `--push`, and lists them with `--dry-run` or `--untagged`, with `--since`, `--package`, `--version` and `--release-title` (or the `releaseTitle` setting); each tag reports its title, previous tag, status and release notes, from the changelog or else the commits since the previous tag. `version --package` versions only some packages and `version --snapshot <id>` releases timestamped snapshots. The `remote` and `baseBranch` settings, with `--remote` and `--base-branch`, set the default comparison of `status` and `add`. `status --since <ref>` fails with exit code 2 for each changed package without a changeset added since the ref, and `add --since <ref>` releases those packages. Every command takes `--json` and `--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-format` and `--project-name` options 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: the `changesets` executable is renamed to `changeset`, the `tags` command is replaced by `tag`, which creates the tags (use `tag --untagged` to only list them), `readmeChangelog` is opt-in and no longer inferred from the readme, and releases carry a `changelog` Markdown list instead of the `notes` array. The documentation moves to the package `docs/` directory, with GitHub Actions workflows for the pull request check, release pull requests and GitHub releases. ([`486b4aa`](https://github.com/wpelevator/basement/commit/486b4aac96b786f75f302b3d9e420a75c3b1b6bd))

## 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`](https://github.com/wpelevator/basement/commit/aa18298e77ea13cb760f63f6e331f17c06f12191))

## 0.1.1 (2026-10-29)

- Document the package release repository after its first tagged release. ([`baa3b0f`](https://github.com/wpelevator/basement/commit/baa3b0fa9878ddea55eb18dcb2c657e24241d9df))

