Release version 1.0.0

[jeffpaul]

Describe your question

This issue is for tracking changes for the 1.0.0 release. :tada: Target release date: April 2022.

Pre-release steps

• [x] add Code of Conduct file
• [x] add Contributing Guidelines and Release Instructions file
• [x] add Changelog file
• [x] add Credits file
• [x] add Support Level

Release steps

• [x] Branch: Starting from develop, cut a release branch named release/1.0.0 for your changes.
• [x] Version bump: Bump the version number in wpcli-vulnerability-scanner.php if it does not already reflect the version being released.
• [x] Changelog: Add/update the changelog in CHANGELOG.md.
• [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.
• [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 latest stable release.
• [x] Push: Push your trunk branch to GitHub (e.g. git push origin trunk).
• [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] Close the 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 1.0.0 do not make it into the release, update their milestone to 1.1.0, or Future Release.

Post-release steps

• [x] Ensure release publishes to npm
• [x] Investigate automation in publishing future releases to npm

Code of Conduct

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

[jeffpaul]

Reopened for @cadic to work on the final steps in the release process

[cadic]

@jeffpaul the remaining steps are complete

[cadic]

@jeffpaul FYI, the release was pushed to https://packagist.org/packages/10up/wpcli-vulnerability-scanner#1.0.0 automatically