Release/1.2.2

[dkotter]

Description of the Change

Version bump and prep for the 1.2.2 release

Closes #106

How to test the Change

Verify all file changes look accurate and tests pass

Changelog Entry

n/a

Credits

Props @dkotter

Checklist:

• I agree to follow this project's Code of Conduct.
• I have updated the documentation accordingly.
• I have added Critical Flows, Test Cases, and/or End-to-End Tests to cover my change.
• All new and existing tests pass.

[jeffpaul]

Looks good, thanks for handling the release!

[jeffpaul]

Seeing some test failures for wordfence and wpscan, worth checking those to see if there's something amiss that we need to account for here.

cc: @felipeelia @burhandodhy @iamdharmesh (as folks who helped on the primary PRs on the release)

[dkotter]

Seeing some test failures for wordfence and wpscan, worth checking those to see if there's something amiss that we need to account for here.

I've fixed the Wordfence failures so we're good there. Looks like the output they return has changed slightly, which is what we look for in our tests, so had to update the test to account for that.

For WPScan, these are failing due to our API key not having access: ERROR_API_QUOTA_FULL: exceed daily rate limit hit. Not sure how to resolve this one without getting a paid API key

[jeffpaul]

I've reached out to WPScan to see if we can get a slightly elevated account above the 25 API daily calls limit.

[dkotter]

I've reached out to WPScan to see if we can get a slightly elevated account above the 25 API daily calls limit.

Do we want to proceed with the release here or wait for that API increase first?

[jeffpaul]

I'm fine proceeding as I don't expect to hear back too quickly from WPScan on increased API limit.