[x] Branch: Starting from develop, cut a release branch named release/3.1.0 for your changes.
[x] Version bump: Bump the version number in classifai.php, config.php, package-lock.json, package.json, and readme.txt if it does not already reflect the version being released.
[x] Changelog: Add/update the changelog in 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 in README.md and readme.txt.
[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] Wait for build: Head to the Actions tab in the repo and wait for it to finish if it hasn't already. If it doesn't succeed, figure out why and start over.
[x] Check the build: Check out the stable branch and test for functionality locally
[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 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 (e.g. https://github.com/10up/classifai/milestone/27?closed=1).
[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 3.0.1 do not make it into the release, update their milestone to 3.2.0 or Future Release.
[x] Version bump (again): In the develop branch (cd ../ && git checkout develop) bump the version number in classifai.php to 3.2.0-dev. It's okay if the next release might be a different version number; that change can be handled right before release in the first step, as might also be the case with @since annotations.
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 3.1.0 release. Target release date: June 2024.
Pre-release steps
Release steps
develop, cut a release branch namedrelease/3.1.0for your changes.classifai.php,config.php,package-lock.json,package.json, andreadme.txtif it does not already reflect the version being released.CHANGELOG.md.CREDITS.mdfile with any new contributors, confirm maintainers are accurate.README.mdandreadme.txt..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.stablebranch and test for functionality locallystablebranch. 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/classifai/milestone/27?closed=1).Due date (optional)field) and link to GitHub release (in theDescriptionfield), then close the milestone.3.0.1do not make it into the release, update their milestone to3.2.0orFuture Release.developbranch (cd ../ && git checkout develop) bump the version number inclassifai.phpto3.2.0-dev. It's okay if the next release might be a different version number; that change can be handled right before release in the first step, as might also be the case with@sinceannotations.Code of Conduct