[x] Branch: Starting from develop, cut a release branch named release/1.2.0 for your changes.
[x] Version bump: Bump the version number in insecure-content-warning.php, readme.txt, package.json and package-lock.json if it does not already reflect the version being released. Update both the plugin "Version:" property and the plugin INSECURE_CONTENT_VERSION constant in insecure-content-warning.php.
[x] Changelog: Add/update the changelog in CHANGELOG.md and readme.txt
[x] Props: update CREDITS.md file with any new contributors, confirm maintainers are accurate
[x] New files: Check to be sure any new files/paths that are unnecessary in the production version are included in .distignore.
[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] 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/insecure-content-warning/milestone/7?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 WordPress.org. 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 1.2.0 do not make it into the release, update their milestone to 1.2.1, 1.3.0 or Future Release.
This issue is for tracking changes for the 1.2.0 release. Target release date: October 2023
Release steps
develop, cut a release branch namedrelease/1.2.0for your changes.insecure-content-warning.php,readme.txt,package.jsonandpackage-lock.jsonif it does not already reflect the version being released. Update both the plugin "Version:" property and the pluginINSECURE_CONTENT_VERSIONconstant ininsecure-content-warning.php.CHANGELOG.mdandreadme.txtCREDITS.mdfile with any new contributors, confirm maintainers are accurate.distignore.README.mdis geared toward GitHub andreadme.txtcontains WordPress.org-specific content. The two are slightly different.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.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/insecure-content-warning/milestone/7?closed=1).Due date (optional)field) and link to GitHub release (in theDescriptionfield), then close the milestone.1.2.0do not make it into the release, update their milestone to1.2.1,1.3.0orFuture Release.