Release version 2.1.0

[Sidsector9]

Is your enhancement related to a problem? Please describe.

This issue is for tracking changes for the 2.1.0 release. Target release date: June 1 2023.

Release steps

• [x] Branch: Starting from develop, cut a release branch named release/2.1.0 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] Compare trunk 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] 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/19?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] Check WordPress.org: Ensure that the changes are live on https://wordpress.org/plugins/safe-redirect-manager/. This may take a few minutes.
• [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.1.0 do not make it into the release, update their milestone to 2.1.1 or Future Release.

Designs

No response

Describe alternatives you've considered

No response

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[jeffpaul]

@Sidsector9 note that the ideal process is to merge the release PR as part of step 7 above