Release 1.3.4

[jeffpaul]

Describe your question

Release steps

• Branch: Starting from develop, cut a release branch named release/1.3.4 for your changes.
• Version bump: Bump the version number in package-lock.json, package.json, publisher-media-kit.php, readme.txt, and any other relevant files if it does not already reflect the version being released. Update both the plugin "Version:" property and the plugin PUBLISHER_MEDIA_KIT_VERSION constant in publisher-media-kit.php.
• Changelog: Add/update the changelog in CHANGELOG.md and readme.txt. (Recommendation to use: https://github.com/10up/changelog-generator)
• If required, Add a note in the CHANGELOG.md and readme.txt files about the min required versions that are bumped, for example: Note that this release bumps the minimum required version of WordPress from 5.5 to 5.7 and PHP from 7.0 to 7.4.
• Props: update the CREDITS.md file with any new contributors, and confirm maintainers are accurate. (Recommendation to use: https://github.com/10up/credits-generator)
• New files: Check to be sure any new files/paths that are unnecessary in the production version are included in .distignore.
• 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.
• Make sure the release date is added in the CHANGELOG.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 trunk (git checkout trunk && git merge --no-ff develop). trunk contains the stable development version.
• Push: Push your trunk branch to GitHub (e.g. git push origin trunk).
• Test the pre-release ZIP locally by downloading it from the Build release zip action artifact to ensure the plugin doesn't break after release.
• 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.
• 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/publisher-media-kit/. This may take a few minutes.
• 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.
• Punt incomplete items: If any open issues or PRs which were milestoned for 1.3.4 do not make it into the release, update their milestone to 1.4.0 or Future Release.

Code of Conduct

• I agree to follow this project's Code of Conduct