Changelog
What changed in each release.
0.21.1 (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) - 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) - Reorganize the documentation by task, with real command output at the top of each page: a quickstart, pages to build a ZIP, check versions, write checksums, verify and sign, a guide to releasing from GitHub Actions, and separate pages to deploy to WordPress.org, Git repositories and configured packages, to release a monorepo, to make pre-releases and snapshots, and to extract and compile translations. Add a command reference grouped by task and a config reference. (
4e6600f) - Bundle checksums 0.1.1.
- Bundle fileset 0.1.1.
- Bundle signatures 0.1.1.
- Bundle subtree-split 0.2.3.
- Bundle wp-gettext 0.2.2.
- Bundle zip 0.1.1.
0.21.0 (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) - Document complete release workflows for single-package repositories, with the
--github-outputresult shapes ofchangeset versionandchangeset tag, the push-triggeredchangeset tag --since HEAD^1idiom and the distribution setups that decide what a release tag must contain. (0bb0b18) - Bundle subtree-split 0.2.2.
- Bundle wp-gettext 0.2.1.
0.20.2 (2026-11-07)
- Publish the
docs/directory in the npm package, so that agents and editors can read the documentation of the installed version. (da8652c) - Bundle subtree-split 0.2.1.
0.20.1 (2026-11-04)
- Bundle subtree-split 0.2.0.
0.20.0 (2026-11-03)
- Split the history of a package for
deploy-git --split-prefixwith@wpelevator/subtree-splitinstead of runninggit subtree split, which makes the same commits in about a tenth of a second instead of several seconds for each package. The full history is needed, so a shallow clone fails. (1498645) - Bundle subtree-split 0.1.0.
0.19.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) - Release the 0.18.2 changes to npm. The 0.18.2 publish failed because building wp-release needed the
dist/of the workspace packages it depends on; it now type-checks their source instead. (621c656) - Bundle wp-gettext 0.2.0.
0.18.2 (2026-10-29)
- Use the new @wpelevator/fileset and @wpelevator/checksums packages for file selection, directory syncing and checksums manifests. The library API, CLI flags, output and manifest bytes are unchanged. Git
export-ignorepaths that contain glob characters like*,?or[are now matched literally instead of as patterns. (16bf135) - Use the new @wpelevator/wp-gettext package for string extraction, POT files and translation compilers. The library API, the
i18n-*command flags and output and the generated POT, MO, JSON and.l10n.phpbytes are unchanged. (16bf135) - Use the new @wpelevator/zip package for ZIP archives. The library API, the
zipcommand flags and output are unchanged, except thatSOURCE_DATE_EPOCHnow sets the modification time of the archive entries when it's set. (16bf135) - Use the new @wpelevator/signatures package for signing. The library API, CLI flags and output, and the WP_RELEASE_SIGNING_KEY variable are unchanged. (
16bf135) - Bundle checksums 0.1.0.
- Bundle fileset 0.1.0.
- Bundle signatures 0.1.0.
- Bundle wp-gettext 0.1.0.
- Bundle zip 0.1.0.
0.18.1 (2026-10-29)
- Expose configured package metadata and tag formatting for the documentation build. (
033c5c2)
0.18.0 (2026-10-29)
- Explain a git-tag version source that finds no tags: name the pattern, an example tag, the checked-out history, and the tagFormat that names release tags. (
a6f60dc) - Add --project-name to name a config-free root package instead of using its manifest name or checkout directory, and an id config to name the package of a group with a literal identifier. (
a6f60dc) - Add changeset-tag --release-title to fill the release titles of one run, replacing the releaseTitle of the config. (
a6f60dc) - Add a releaseTitle config for release titles, a template or callback with the name, path, version and tag of a release. A package at the repository root is titled with its version like its tag, without a name or path prefix, and an empty path leaves no leading or repeated slashes. (
a6f60dc) - Release the sole package of a repository without --package options, with a single changeset-add --bump and with changeset-tag --version. (
a6f60dc) - Reject positional arguments that the command doesn't accept instead of ignoring them, so a stray word fails with the usage instead of running another command flow. (
a6f60dc)
0.17.0 (2026-10-13)
- Add native WordPress POT extraction and auditing, with the POT layout of
wp i18n make-pot, plus translated PO compilation into MO, script JSON and .l10n.php with reproducible atomic outputs. (6cd4598)
0.16.0 (2026-10-13)
- Make ZIP and manifest signing independent: --sign signs only ZIPs, --sign-checksums generates and signs manifests for ZIPs and directory builds, and --sign-format requires an explicit signing target. Update the ZIP Action and release examples. (
e515a53) - Add a build command that copies selected release files into an output directory using the same ignore and configured package rules as ZIP packaging. (
e515a53) - Expose checksum filenames, formats, embedding and configured signing overrides in the release actions. Separate embedded metadata outputs from uploadable files and align action examples, verification and CI instructions with the coordinated release. (
4b3e411) - Add independent checksum filenames, embedded signed manifests, GNU SHA256SUMS and custom manifest codecs with configuration and verification support. (
fd95713) - Release single-project repositories without a config file, with shared changeset CLI options for version files, PHP constants, Git tag sources and changelog settings. (
9c3d34b)
0.15.0 (2026-10-13)
-
Add ZIP signing inputs and signature outputs, expose WordPress, minisign and SSH formats in the sign action, and update action documentation to match wp-release.
Support configured SVN deployment with release-ref, package, list, config and tag-format inputs, preserve single-plugin deployment outputs, and expose configured plans and outcomes as JSON. Add the ZIP config input. Run the SVN action through the shared command with an injected runner that installs SVN only when needed. (
ff25f51) -
Set each top-level string, number or boolean of a result as its own GitHub Actions step output with
--github-output, next to theresultJSON, so that a workflow reads values likesteps.<id>.outputs.zipPathwithoutfromJSON(), also in steps that are skipped. Addzip --signto sign the ZIP and the checksums manifest as they're written, with--sign-formatfor the signature formats ofsign --format, andsignFiles()to sign files from a script.Validate the signing key, formats and existing signature destinations before writing a signed ZIP or manifest, so invalid signing inputs leave no new artifacts and can be corrected without forcing an overwrite. Include the signature files and public keys in the job summary of
zip --sign. (afd7d94)
0.14.0 (2026-10-13)
- Report the
target,targetRefand, for remote repositories, thetargetHostandtargetPathof each deploy in thedeploy-gitanddeploy-svn --release-refresults, and thehostandpathof the targets of--list, so that a workflow can create the release of the deployed tag with the API of the forge that hosts the repository.parseRepositoryUrl()reads the host and path of a repository URL. (f8b330e) - Make the config layer independent of the repository layout. Remove the
{type}placeholder and thetagTypepackage group setting, which guessed a type from the first directory of the package path, and the{slug}placeholder of the tag format, version source patterns and deploy templates; use{path}, like{path}/{version}forplugins/alpha/1.2.0, or a callback. A package at the repository root has an empty{path}, and tags have no leading or repeated slashes, so the default{path}/{version}tag format gives it tags like1.2.0. The WordPress.org slug of an SVN deploy target defaults to the name of the package directory. Add the global--tag-format <format>option to replace thetagFormatof the config for one command, and theremotesetting for the git remote thatchangeset-tag --pushpushes to and that the base branch is compared on,originby default. (f8b330e) - Sign files as minisign (
.minisig) and SSH (.sshsig) signatures withsign --format, using the same Ed25519 key as the WordPress.sig.verify --signature-formatchecks the manifest signature of those formats,verify --public-keyalso accepts minisign andssh-ed25519public keys, andkeygenprints the public key in both forms. (7d641fd) - Add
zip --package <name>to zip a package of the config with thefilesconfig of its package group, the same files that its deploys ship, andzipPackage()andgetPackageFiles()to build the same ZIP from a script. Thezipresult also has theslugandversion. (f8b330e)
0.13.0 (2026-10-12)
- Ask for the packages, bumps and release note of
changeset-addin a terminal, preselecting the changed packages; add the changed packages with a single--bump; and accept package paths inchangeset-add,changeset-versionandchangeset-tag. (9359398) - Add
deploy-git --release-ref <ref>anddeploy-svn --release-ref <ref>to deploy the configured packages of a release tag or branch to the Git and WordPress.org targets in the newdeployconfig of their package groups, with--packageto deploy one package and--listto list the deploys. Targets take templates or callbacks with the package, its release and the source commit, also for the commit message, and a list of them deploys to several repositories. The newfilesconfig sets the files that the deploys ship, and package groups withoutversiononly deploy branches, without changesets. (0f520f8) - Require a changeset for a dependent whose package manifest changes beyond the pin of a source that the pull request releases. (
1fa3644) - Add
changeset-version --prerelease <id>and theprereleaseoption ofversionChangesets()to release pre-releases like1.3.0-rc.1, numbered from the package tags, and--snapshot <id>for test builds like1.3.0-pr-251.20261012183005. The readmeStable tagkeeps the last stable version for a pre-release, and the release notes of a stable release compare with the previous stable release instead of its pre-releases. (40c4283) - Bump the
x.yandx.y.z.wversions common in WordPress plugins without a customnextVersionstrategy. A version keeps its number of parts, so a minor bump of2.1is2.2and of1.2.3.4is1.3.0.0, while a patch bump of2.1is2.1.1. Tags with these versions are now sorted and found as the previous release, comparing every part. (e64fc2f)
0.12.0 (2026-10-12)
- Remove the
getGitHubPullRequest()export, so wp-release no longer needs theghCLI. AchangelogEntrycallback can link each entry to the commit that added its changeset with thecommitit receives. (f463fc7)
0.11.0 (2026-10-12)
- Add the
ChangesetReleaseclass, which runs the changeset release operations with an injectable git runner. The changeset release code is split into focused modules, and the README documents the package architecture. (#242 by @kasparsd,bf1279d) - Remove the
--github-releaseflag ofchangeset-tagand thegithubReleaseoption oftagChangesets(); create GitHub Releases with a workflow step likesoftprops/action-gh-releaseinstead. Each tag in thechangeset-tagresult now has atitle, likeplugins/alpha@1.2.0, for that step. (#242 by @kasparsd,bf1279d) - Detect the changes of a package at the repository root, so that
changeset-statusreports its missing changesets andchangeset-tag --sincetags it. (#242 by @kasparsd,bf1279d)
0.10.0 (2026-10-12)
- Add a
dependentschangeset configuration, which re-releases packages that bundle another configured package whenever it releases, so that bundled dependencies like thewp-release-*GitHub Actions ship the new version at the same time. The dependents come from the dependencies that each package declares inpackage.json: a dependent releases when the next version of the source falls outside its declared range, or always withwhen: 'always', and versioning rewrites its declared specs of the source to the released version, keeping their range prefixes. Dependents release with abumpbump (defaultpatch) and a "Bundle." changelog entry unless they have their own changeset, --packageselections pull in the dependents of the selected sources, anddependents.excludeleaves packages out of the automatic re-releases, while they still release with their own changesets, and versioning a dependent while a dependency it declares has pending changesets fails, so a release can't bundle unreleased source code;--no-dependentsskips the dependents and the check. Thedependents.dependencyhooks add specs of couplings that other manifests declare to the built-in npm scan, and replace its spec rewrite, so that the same range rule and rewrite apply to them. (#238 by @kasparsd,04fa1be)
0.9.0 (2026-10-12)
- Add
keygenand opt-in Gitexport-ignoresupport to release file selection. (#234 by @kasparsd,1eb51e4)
0.8.0 (2026-10-11)
- New
changelogEntryconfig callback, which formats the changelog entry of each changeset with the commit that added it, for example to credit its pull request and author. The formatted entries go intoCHANGELOG.md, thechangeset-versionresult and the release notes. New library exports:getGitHubPullRequest(), which finds the pull request and author of a commit with theghCLI, andformatChangelogList(). (#228 by @kasparsd,7fce8f7)
0.7.0 (2026-10-11)
- New library exports:
GitDeploy,resolveGitDeployOptions(),isValidRefName(),createGitRunner(),GitError,redactUrls()andgetGitDeployInputFromArgs(), with theGitDeployInput,GitDeployOptions,GitDeployResult,GitRunner,GitCommandInputandGitCommandOutputtypes. - New
deploy-gitcommand, which deploys the files of a plugin, theme or package to a Git repository as a release commit, selected likezipwith.distignoreand--exclude. The release commit's parents are the previous release and the source history, the source commit or with--split-prefixthe history of a monorepo package fromgit subtree split, so the repository keeps the history. Pushes are never forced: the branch only moves forward, releases without changes aren't pushed, an older build that runs again doesn't move the branch back to older files, a tag that already has the same files is reused without pushing, and a tag with other files fails with exit code 2 before anything is pushed. changeset-tagcan release a single package with--package <name>and check its version with--version <version>. It checks that every configured version target matches before it creates a tag, marks the GitHub Releases of pre-release versions like1.0.0-rc.1as pre-releases, falls back to the commits since the previous tag for the release notes when the version has noCHANGELOG.mdsection, prints the release notes in dry runs and adds the tags to the job summary. The newreleaseNotesconfig callback formats the release notes, for example to add links. Thechangeset-versionresult has the changelog entries of each release, and its job summary lists the package releases.changeset-version --package <name>versions only the named packages: a changeset that also names other packages keeps only their entries, so it still applies to their releases. New library exports:getChangesetPackages()andformatChangelogEntries().
0.6.1 (2026-10-11)
- Push release tags one at a time with
changeset-tag --push, so that GitHub triggers tag workflows for each of them, addchangeset-tag --untaggedto list the releases that don't have a tag yet, and add the global--github-outputoption to set the command result as a GitHub Actions step output.
0.6.0 (2026-10-11)
- Keep the release actions pinned to a stable wp-release version while the monorepo root resolves them to its local workspace; support explicit changelog insertion markers before the first version heading.
- Add experimental Changesets-compatible release commands and JavaScript configuration for WordPress plugins, themes, PHP packages, and JavaScript packages.
0.5.0 (2026-10-11)
- With the
githublog format,version-checkanddeploy-svnannotate each version mismatch on the file and line of theVersionheader, readmeStable tagor PHP constant, andverifyreports changed files and files that aren't in the checksums as problems on their files. - Workflow command messages are escaped, so a multi-line error stays one annotation.
ValidationErrorcan listproblemswith a file and line, andlogError()reports each one on its own file and line.deploy-svnthrows aVersionMismatchError, aValidationErrorwith themismatchesand their problems, when the versions don't agree. The message is unchanged.VersionMismatchhas thelineof the version.- With the
githublog format,deploy-svn,zip,checksums,sign,verifyandversion-checkadd a section to the job summary of the run whenGITHUB_STEP_SUMMARYis set. A deploy summary links the plugin to its WordPress.org page and the commit to its changeset, and lists the SVN changes. Failed commands add their error, and version mismatches add a table with their files and lines. Loggerpasses messages to a writer instead of formatting them:new Logger( { writer: new GitHubActionsWriter() } )replacesnew Logger( { ci: true } ), andTextWriteris the default. Theci,stdoutandstderroptions moved to the writers, andLoggerno longer readsGITHUB_ACTIONS.error(),warning()andnotice()take an annotation with afile,lineandtitle, andsummary()takes a function that builds the summary Markdown.- New
--log-format <text|github>option that picks how the CLI logs. It defaults togithubwhenGITHUB_ACTIONS=true, as--cidocumented, and totextelsewhere.--ciis a shorthand for--log-format github, and--log-format textprints plain text in GitHub Actions. Before, annotations needed--ci. - New library exports:
TextWriter,GitHubActionsWriter,logError(),logProblems(),VersionMismatchError,getVersionMismatchProblems(),findConstantDefinitions(),findFileHeaderLine(),findReadmeHeaderLine(), and theLogWriter,LogEntry,SummaryBuilder,SummaryContext,AnnotationandProblemtypes. The Markdown helpers that build the summaries stay internal.
0.4.1 (2026-10-10)
verify --embedded <path>now requires both the--checksumsfile and its.signext to it, and both shipped copies, instead of passing when the signature is absent on both sides. It fails when the manifest lists the embedded path.verifywithout--embeddedskips a manifest or.sigcopy at the root only when the copy exists, the matching original exists and the manifest doesn't list it. Before, a file with the name of the manifest was ignored in both the directory and the manifest, so a listed file likechecksums.jsoncould be deleted without being noticed, and a shipped.sigwithout an original was skipped instead of reported as not in the checksums.
0.4.0 (2026-10-10)
deploy-svn --svn-tagwithout--trunknow builds the tag from the source files instead of copying the repository's trunk, so a pre-release like1.5.1-rc.1can be tagged without touching trunk. The tag run checks that theVersionheader matches the tag, but not the readmeStable tag. With--force, an existing tag is updated to match the build.--trunk --svn-tagstill copies the synced trunk.checksums,zipandverifyskip the.signext to the manifest or ZIP they write, so a signed manifest can be shipped inside the plugin.- New
verify --zip <file|url>and--root-folderoptions check the files of a ZIP, including one downloaded from a URL such as the ZIP that WordPress.org builds for a release. verifyskips a copy of the manifest and its.sigat the root of the checked files, and fails when the copy differs from the--checksumsfile.- New
verify --embedded <path>option for a manifest and signature shipped at another path than the root. The copies must exist and match the--checksumsfile and its.sig. checksums --outputcreates missing folders.verifyfails when the version in the manifest differs from theVersionheader of the checked files.- New
signcommand, which writes a detached Ed25519<file>.sigof the SHA-384 digest in the format that WordPress core'sverify_file_signature()checks. The key comes from theWP_RELEASE_SIGNING_KEYenvironment variable. - New
verify --public-keyoption, which checks the signature of the checksums manifest before comparing any file. - New library exports for signing (
signFile(),writeSignature(),verifyFileSignature(),parseSigningKey(),parsePublicKey(),getPublicKey()) andexecute()to run a command by name and get its result, which the GitHub Actions use.
0.3.0 (2026-10-10)
- Pre-release versions like
1.5.1-rc.1can now be used as an SVN tag. Syncing a pre-release version totrunk/still warns. - Restored
deploy-svn --readme-only, which 0.2.0 removed. It syncs only the readme totrunk/for updates between releases, and can't be combined with--svn-tag. ThegitRefdeploy option stays removed.
0.2.0 (2026-10-09)
deploy-svn --svn-tagno longer requires--trunk. Without--trunk, the tag is copied from the currenttrunk/in the repository, without checking out trunk. With--trunkthe tag is copied from the working copy, so it includes the changes of the run.- Removed
deploy-svn --readme-only: a deploy writes the whole trunk or nothing to it. Assets can still be updated alone with--assets-dir. - Removed the
gitRefdeploy option, which only guarded--readme-only.
0.1.1 (2026-10-09)
- First release published by the release workflow with npm trusted publishing. No changes to the package.
0.1.0 (2026-10-09)
- First release with the
zip,checksums,verify,version-checkanddeploy-svncommands.