Is your enhancement related to a problem? Please describe.
This issue is for tracking changes for the 1.3.0 release. Target release date: TBD.
[x] Branch: Starting from develop, cut a release branch named release/1.3.0 for your changes.
[x] Version bump: Bump the version number in package-lock.json, package.json, readme.txt, and retro-winamp-block.php if it does not already reflect the version being released.
[x] Changelog: Add/update the changelog in CHANGELOG.md and readme.txt.
[x] Props: update CREDITS.md 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 (git checkout trunk && git merge --no-ff develop). trunk contains the stable development version.
[x] Test: Run through common tasks while on trunk to be sure it functions correctly. Don't forget to build.
[x] Push: Push your trunk branch to GitHub (e.g. git push origin trunk).
[x] 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.
[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.
[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] Close the milestone: Edit the X.Y.Z 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 X.Y.Z do not make it into the release, update their milestone to 2.0.0, 1.4.0, 1.3.1, or Future Release
Code of Conduct
[X] I agree to follow this project's Code of Conduct
Is your enhancement related to a problem? Please describe.
This issue is for tracking changes for the 1.3.0 release. Target release date: TBD.
develop, cut a release branch namedrelease/1.3.0for your changes.package-lock.json,package.json,readme.txt, andretro-winamp-block.phpif it does not already reflect the version being released.CHANGELOG.mdandreadme.txt.CREDITS.mdwith 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(git checkout trunk && git merge --no-ff develop).trunkcontains the stable development version.trunkto be sure it functions correctly. Don't forget to build.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.Due date (optional)field) and link to GitHub release (in theDescriptionfield), then close the milestone.X.Y.Zdo not make it into the release, update their milestone to2.0.0,1.4.0,1.3.1, orFuture ReleaseCode of Conduct