Release version 1.5.0

[jeffpaul]

This issue is for tracking changes for the 1.5.0 release. Target release date: Thursday, February 27th.

Pre-release steps

• Resolve issues in PR Process Existing Images with Computer Vision #135 and merge
• Complete review of PR Fix: Pages are not being scanned by Language Processing #164, resolve issues, and merge
• Complete review of PR Add: WP-CLI command to bulk classify images #177, resolve issues, and merge
• Complete review of PR Add: Ability to process already created content #178, resolve issues, and merge
• Complete review of PR Add: WP Acceptance #179, resolve issues, and merge (if necessary, this is a candidate to punt and resolve after the release)

Release steps

• Branch: Starting from develop, cut a release branch named release/1.5.0 for your changes.
• Version bump: Bump the version number in classifai.php, config.php, package-lock.json, package.json, and classifai.pot if it does not already reflect the version being released.
• Changelog: Add/update the changelog in CHANGELOG.md.
• Translations: Update the .pot file by running npm run makepot.
• Props: update CREDITS.md file with any new contributors, confirm maintainers are accurate
• New files: Check to be sure any new files/paths that are unnecessary in the production version are included in .github/action-release/rsync-filter.txt.
• Readme updates: Make any other readme changes as necessary in CHANGELOG.md and README.md.
• 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 master (git checkout master && git merge --no-ff develop). master contains the stable development version.
• Push: Push your master branch to GitHub (e.g. git push origin master).
• 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.
• Check the build: Check out the stable branch and test for functionality locally.
• 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 1.5.0 milestone. The release should now appear under releases and in the WordPress admin as an update as well.
• Close milestone: Edit the 1.5.0 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 1.5.0 do not make it into the release, update their milestone to 1.5.1, 1.6.0, 2.0.0 or Future Release.

[jeffpaul]

Noting here that the release process errored out here: https://github.com/10up/classifai/runs/472927828?check_suite_focus=true. Which relates to this step in the release process:

classifai/.github/action-release/entrypoint.sh

Line 19 in f00818a

echo "ℹ︎ Configuring git"

. My suspicion is that the https://github.com/10upbot account is no longer in the 10up org or with access to ClassifAI and causing the failure, but I'll review next week when necessary folks are around to chat with. Apologies for the delay on the release.

[helen]

I think this may need a git fetch origin before it does the worktree bit, can try it from a branch off master and see if it runs correctly upon merge.

[ryanwelcher]

1.5.0 is live https://github.com/10up/classifai/releases/tag/1.5.0