[x] 1. If the new version requires a reindex, add its number to the $reindex_versions array in the ElasticPress\Upgrades::check_reindex_needed() method. If it is the case, remember to add that information to the Changelog listings in readme.txt and CHANGELOG.md.
[x] 2. Branch: Starting from develop, cut a release branch named release/5.1.1 for your changes.
[x] 3. Version bump: Bump the version number in elasticpress.php, package.json, package-lock.json, readme.txt, and any other relevant files if it does not already reflect the version being released. In elasticpress.php update both the plugin "Version:" property and the plugin EP_VERSION constant.
[x] 5. Props: Update CREDITS.md file with any new contributors, confirm maintainers are accurate.
[x] 6. 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] 7. New files: Check to be sure any new files/paths that are unnecessary in the production version are included in .distignore.
[x] 8. POT file: Run wp i18n make-pot . lang/elasticpress.pot and commit the file. In case of errors, try to disable Xdebug (see #3079.)
[x] 9. Release date: Double check the release date in both changelog files.
[x] 10. Merge: Merge the release branch/PR into develop, then make a non-fast-forward merge from develop into trunk (git checkout trunk && git merge --no-ff develop). trunk contains the stable development version.
[x] 11. Test: While still on the trunk branch, test for functionality locally.
[x] 12. Push: Push your trunk branch to GitHub (e.g. git push origin trunk).
[x] 13. Check the Build and Tag action: a new tag named with the version number should've been created. It should contain all the built assets.
Description: Release changelog from CHANGELOG.md + See: https://github.com/10up/ElasticPress/milestone/84?closed=1
[x] 15. 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] 17. 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] 18. Punt incomplete items: If any open issues or PRs which were milestoned for 5.1.1 do not make it into the release, update their milestone to 5.1.2, 5.2.0, 6.0.0 or Future Release
$reindex_versionsarray in theElasticPress\Upgrades::check_reindex_needed()method. If it is the case, remember to add that information to the Changelog listings inreadme.txtandCHANGELOG.md.develop, cut a release branch namedrelease/5.1.1for your changes.elasticpress.php,package.json,package-lock.json,readme.txt, and any other relevant files if it does not already reflect the version being released. Inelasticpress.phpupdate both the plugin "Version:" property and the pluginEP_VERSIONconstant.CHANGELOG.mdandreadme.txt, ensuring to link the [5.1.1] release reference in the footer ofCHANGELOG.md(e.g., https://github.com/10up/ElasticPress/compare/5.1.0...5.1.1).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..distignore.wp i18n make-pot . lang/elasticpress.potand commit the file. In case of errors, try to disable Xdebug (see #3079.)develop, then make a non-fast-forward merge fromdevelopintotrunk(git checkout trunk && git merge --no-ff develop).trunkcontains the stable development version.trunkbranch, test for functionality locally.trunkbranch to GitHub (e.g.git push origin trunk).Version 5.1.1CHANGELOG.md+See: https://github.com/10up/ElasticPress/milestone/84?closed=1Due date (optional)field) and link to GitHub release (in theDescriptionfield), then close the milestone.5.1.1do not make it into the release, update their milestone to5.1.2,5.2.0,6.0.0orFuture Release