Release: 2.2.0

[github-actions]

This issue is for tracking changes for the 2.2.0 release. Target release date: September 2025.

Pre-release steps

• Determine progress on Fix/1144 webp support #1269
• Rebase to develop and merge Fix broken images #1319
• Determine progress on Auto Distribution feature. #1321

Release steps

• Branch: Starting from develop, create a release branch named release/2.2.0 for your changes.
• Version bump: Bump the version number in distributor.php, package-lock.json, package.json, readme.txt and tests/php/bootstrap.php if it does not already reflect the version being released. In distributor.php update both the plugin "Version:" property and the plugin DT_VERSION constant.
• Changelog: Add/update the changelog in CHANGELOG.md.
• Props: Update CREDITS.md file with any new contributors, confirm maintainers are accurate.
• Readme updates: Make any other readme changes as necessary. README.md is geared toward GitHub and readme.txt contains WordPress.org-specific content. The two are slightly different.
• New files: Ensure any new files, especially in the vendor folder, are correctly included in webpack.config.release.js.
• Since tag updates: ensure @since tags indicate the new version, replacing x.x.x, n.e.x.t and other placeholders.
• Merge: Make a non-fast-forward merge from your release branch to develop (or merge the Pull Request), then do the same for develop into trunk (git checkout develop && git pull origin develop && git checkout trunk && git pull origin trunk && git merge --no-ff develop). trunk contains the stable development version.
• Push: Push your trunk branch to GitHub (e.g. git push origin trunk).
• Compare trunk to develop to ensure no additional changes were missed.
• Build: Wait for the Build Stable Release Action to finish running.
• Review: Do a review of the commit to the stable branch to ensure the contents of the diffs are as expected.
• Test: Check out the stable branch and test it locally to ensure everything works as expected. It is recommended that you rename the existing distributor directory and check out stable fresh because switching branches does not delete files. This can be done with git clone --single-branch --branch stable [email protected]:10up/distributor.git
• Either perform a regression testing utilizing the available Critical Flows and Test Cases or if end-to-end tests cover a significant portion of those Critical Flows then run e2e tests. Only proceed if everything tests successfully.
• Release: Create a new release, naming the tag and the release with the new version number, and targeting the stable branch. Paste the changelog from CHANGELOG.md into the body of the release and include a link to the closed issues on the milestone. The release should now appear under releases.
• Check release: Wait for the Publish Release Action to complete, and then check the latest release to ensure that the ZIP has been attached as an asset. Download the ZIP and inspect the contents to be sure they match the contents of the stable branch.
• Close milestone: Edit the milestone with release date (in the Due date (optional) field) and link to GitHub release (in the Description field), then close the milestone.
• Punt incomplete items: If any open issues or PRs which were milestoned for 2.2.0 do not make it into the release, update their milestone to 2.3.0, or Future Release.

[jeffpaul]

@dkotter fine by me if we want to skip those two additional PRs in the pre-release section and proceed with the v2.2 release

[jeffpaul]

Looks good, thanks for handling the release!