Release: 2.0.1

[github-actions[bot]]

• [x] Branch: Starting from develop, create a release branch named release/X.Y.Z for your changes.
• [x] Version bump: Bump the version number in distributor.php, package.json, readme.txt and tests/php/bootstrap.php if it does not already reflect the version being released. In distributor.php update both the plugin "Version:" property and the plugin DT_VERSION constant.
• [x] New files: Ensure any new files, especially in the vendor folder, are correctly included in webpack.config.release.js.
• [x] Changelog: Add/update the changelog in CHANGELOG.md.
• [x] Props: Update CREDITS.md file with any new contributors, confirm maintainers are accurate.
• [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] Since tag updates: ensure @since tags indicate the new version, replacing x.x.x, n.e.x.t and other placeholders.
• [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] Build: Wait for the Build Stable Release Action to finish running.
• [x] Update this pull request's status from draft to ready to merge.
• [x] Review: Do a review of the commit to the stable branch to ensure the contents of the diffs are as expected.
• [x] Test: Check out the stable branch and test it locally to ensure everything works as expected. It is recommended that you rename the existing distributor directory and check out stable fresh because switching branches does not delete files. This can be done with git clone --single-branch --branch stable git@github.com:10up/distributor.git
• [x] 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.
• [x] Check release: Wait for the Publish Release Action to complete, and then check the latest release to ensure that the ZIP has been attached as an asset. Download the ZIP and inspect the contents to be sure they match the contents of the stable branch.
• [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 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.

[jeffpaul]

@peterwilsoncc @dkotter not certain if we similarly need to version bump to 2.0.1 in https://github.com/10up/distributor/blob/46a26fa0b00e3b428f45430e1426d5de5adf7621/includes/rest-api.php#L385 && https://github.com/10up/distributor/blob/46a26fa0b00e3b428f45430e1426d5de5adf7621/includes/classes/ExternalConnections/WordPressExternalConnection.php#L279 or if that was only needed for 2.0.0 (e.g. for folks crossing the v1 to v2 divide)?

[jeffpaul]

@dkotter @peterwilsoncc @ravinderk open to any of the following items currently in the 2.0.1 milestone getting wrapped up, merged, and included in the release:

• [ ] #1002
• [ ] #1003
• [ ] #1073

But come Monday, we'll want to continue with the 2.0.1 in any case to get the fix out for the distributed author issue (and other updates in the release).

[ravinderk]

@jeffpaul I started work on https://github.com/10up/distributor/pull/1073. I will wrap it up by the end of next week.

[peterwilsoncc]

if that was only needed for 2.0.0 (e.g. for folks crossing the v1 to v2 divide)?

Only needed for crossing the divide so no need to bump.