[x] Branch: Starting from develop, cut a release branch named release/2.2.1 for your changes.
[x] Version bump: Bump the version number in safe-redirect-manager.php, package-lock.json, package.json, and readme.txt if it does not already reflect the version being released. In safe-redirect-manager.php update both the plugin "Version:" property and the plugin SRM_VERSION constant.
[x] Changelog: Add/update the changelog in both readme.txt and CHANGELOG.md.
[x] Props: Update CREDITS.md file with any new contributors, confirm maintainers are accurate.
[x] 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.
[x] New files: Check to be sure any new files/paths that are unnecessary in the production version are included in .gitattributes.
[x] 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, ensuring you pull the most recent changes into develop first (git checkout develop && git pull origin develop && git checkout trunk && git merge --no-ff develop). trunk contains the stable development version.
[x] Push: Push your trunk branch to GitHub (e.g. git push origin trunk).
[x] Comparetrunk to develop to ensure no additional changes were missed.
[x] Test the pre-release ZIP locally by downloading it from the Build release zip action artifact and installing it locally. Ensure this zip has all the files we expect, that it installs and activates correctly and that all basic functionality is working.
[x] 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.
[x] Release: Create a new release, naming the tag and the release with the new version number, and targeting the trunk branch. Paste the changelog from CHANGELOG.md into the body of the release and include a link to the closed issues on the milestone (e.g. https://github.com/10up/safe-redirect-manager/milestone/24?closed=1).
[x] SVN: Wait for the GitHub Action to finish deploying to the WordPress.org repository. If all goes well, users with SVN commit access for that plugin will receive an emailed diff of changes.
[x] 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.
[x] Punt incomplete items: If any open issues or PRs which were milestoned for 2.2.1 do not make it into the release, update their milestone to 2.3.0 or Future Release.
Code of Conduct
[x] I agree to follow this project's Code of Conduct
Describe your question
This issue is for tracking changes for the
2.2.1release. Target release date: 13 November 2024.Pre-release steps
Release steps
develop, cut a release branch namedrelease/2.2.1for your changes.safe-redirect-manager.php,package-lock.json,package.json, andreadme.txtif it does not already reflect the version being released. Insafe-redirect-manager.phpupdate both the plugin "Version:" property and the pluginSRM_VERSIONconstant.readme.txtandCHANGELOG.md.CREDITS.mdfile with any new contributors, confirm maintainers are accurate.README.mdis geared toward GitHub andreadme.txtcontains WordPress.org-specific content. The two are slightly different..gitattributes.develop(or merge the pull request), then do the same fordevelopintotrunk, ensuring you pull the most recent changes intodevelopfirst (git checkout develop && git pull origin develop && git checkout trunk && git merge --no-ff develop).trunkcontains the stable development version.trunkbranch to GitHub (e.g.git push origin trunk).trunktodevelopto ensure no additional changes were missed.trunkbranch. Paste the changelog fromCHANGELOG.mdinto the body of the release and include a link to the closed issues on the milestone (e.g.https://github.com/10up/safe-redirect-manager/milestone/24?closed=1).Due date (optional)field) and link to GitHub release (in theDescriptionfield), then close the milestone.2.2.1do not make it into the release, update their milestone to2.3.0orFuture Release.Code of Conduct