Release version 1.1.1

[jeffpaul]

This issue is for tracking changes for the 1.1.1 release. Target release date: TBD

Pre-release steps

• update CREDITS.md file with any new contributors, confirm maintainers are accurate
• review Add note to readme about Gutenberg support #43 to see if a quick PR/review/merge is feasible, if so proceed, if not punt to v1.2.0
• test develop against WordPress 5.3, assuming all goes well, update the "tested up to" value to 5.3
• update GitHub Action workflow to YAML version: https://github.com/10up/eight-day-week/blob/develop/.github/main.workflow

Release steps

• Starting from develop, cut a release branch named release/1.1.1 for your changes.
• Version bump: Bump the version number in eight-day-week.php and readme.txt if it does not already reflect the version being released.
• Changelog: Add/update the changelog in both readme.txt and CHANGELOG.md.
• Check to be sure any new files/paths that are unnecessary in the production version are included in .gitattributes.
• Readme updates: Make any other readme changes as necessary. CHANGELOG.md and README.md are geared toward GitHub and readme.txt contains WordPress.org-specific content. The two are slightly different.
• Merge: Make a non-fast-forward merge from develop to master (git checkout master && git merge --no-ff develop).
• Release: Create a new release, naming the tag and the release with the new version number. 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/eight-day-week/milestone/12?closed=1). Close the milestone.
• 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.
• Check WordPress.org: Ensure that the changes are live on https://wordpress.org/plugins/eight-day-week-print-workflow/. This may take a few minutes.
• Edit the 1.1.1 milestone with release date (in the Due date (optional) field) and link to GitHub release (in the Description field), then close 1.1.1 milestone.
• If any open issues or PRs which were milestoned for 1.1.1 do not make it into the release, update their milestone to 1.2.0 or Future Release.

[jeffpaul]

Done:
https://github.com/10up/eight-day-week/releases/tag/1.1.1
https://plugins.trac.wordpress.org/changeset/2199078/