Release: 2.3.0

[github-actions]

• Branch: Starting from develop, cut a release branch named release/X.Y.Z for your changes.
• Changelog: Add/update the changelog in CHANGELOG.md.
• Props: update CREDITS.md file with any new contributors, confirm maintainers are accurate.
• Readme updates: Make any other readme changes as necessary in README.md.
• Merge: Make a non-fast-forward merge from your release branch to develop (or merge the pull request), then merge develop into stable (git checkout stable && git merge --no-ff develop).
• Push: Push your stable branch to GitHub (e.g. git push origin stable).
• 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 milestone. The release should now appear under releases.
• Ensure the release appears in the GitHub Marketplace correctly.
• 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 X.Y.Z do not make it into the release, update their milestone to X.Y.Z+1, X.Y+1.0, X+1.0.0 or Future Release.
• Celebrate shipping!

[jeffpaul]

Looks good to me, though in the future feel free to lump most of the items noted here into a generic "Documentation updates" changelog entry with the various props/via references there.

[jeffpaul]

Though I guess one question on #160 for repos that already added the svn step to their workflow file, will things work ok for them (I think we've done that already in a couple places)?

[peterwilsoncc]

Though I guess one question on #160 for repos that already added the svn step to their workflow file, will things work ok for them (I think we've done that already in a couple places)?

@jeffpaul Should do, #160 includes a command -v check to only install the command if it isn't available. For repos that have added it to thei build steps, installation will be skipped.

[felixarntz]

Hey all, just stumbled across this. Curious when you're planning to publish this release?

I'm asking since the change with ubuntu-latest is preventing me from deploying plugin releases. I know there's a workaround, but since I saw this I thought it might be worth to just wait for the new release :)

[jeffpaul]

@felixarntz we'll get the release out this week, chasing down some things elsewhere but should be able to get back to this shortly