[Release] Version 2.0.1

[felipeelia]

• 1. Branch: Starting from trunk, cut a release branch named release/2.0.1 for your changes.
• 2. Version bump: Bump the version number in cf7-repeatable-fields.php, package.json, package-lock.json, readme.txt, and any other relevant files if it does not already reflect the version being released. In cf7-repeatable-fields.php update both the plugin "Version:" property and the plugin CF7_REPEATABLE_FIELDS_VERSION constant.
• 3. Changelog: Add/update the changelog in CHANGELOG.md and readme.txt, ensuring to link the [2.0.1] release reference in the footer of CHANGELOG.md (e.g., 2.0.0...2.0.1). Update the Unreleased link to 2.0.1...trunk
• 4. Props: Update CREDITS.md file with any new contributors, confirm maintainers are accurate.
• 5. 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.
• 6. New files: Check to be sure any new files/paths that are unnecessary in the production version are included in .distignore.
• 7. POT file: Run wp i18n make-pot . languages/cf7-repeatable-fields.pot and commit the file. In case of errors, try to disable Xdebug (see this comment.)
• 8. Release date: Double check the release date in both changelog files.
• 9. Merge: Merge the release branch/PR into trunk.
• 10. Test: Run git pull origin trunk and test for functionality locally.
• 11. Release: Create a new release, naming the release and the new tag with the new version number (2.0.1). Paste the release changelog from CHANGELOG.md into the body of the release and include a link to the closed issues on the milestone.
• 12. 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.
• 13. Check WordPress.org: Ensure that the changes are live on https://wordpress.org/plugins/cf7-repeatable-fields/. This may take a few minutes.
• 14. 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.
• 15. Punt incomplete items: If any open issues or PRs which were milestoned for 2.0.1 do not make it into the release, update their milestone to 2.0.1+1, X.Y+1.0, X+1.0.0 or Future Release.