v1.7.1

What's Changed

• Upgrade Node from 16 -> 20 (by @sirLisko in #735, thanks! 🙏 )

New Contributors

• @devnev made their first contribution in #476
• @alagos made their first contribution in #594
• @sirLisko made their first contribution in #735

Full Changelog: v1.7.0...v.1.7.1

v1.7.0

• Fixes #389: once the bot has commented once, it will now update that comment rather than creating new ones.
• Fixes #333: removed trailing period from the end of the default error message.

v1.6.1

• Fixes #266: the success comment will now be created once the PR Lint succeeds, even when on-failed-regex-create-review is set to false. Thank you @talboren for reporting, debugging, and fixing this! 💪

v1.6.0

• Updated documentation to recommend running the action on PR synchronize events too, so that the checks won't go stale.
• Fixes #175: can now customize the success message when reviews are dismissed using on-succeeded-regex-dismiss-review-comment.
• Fixes #171: run action with Node 16.
• Upgrade dependencies.

v1.5.1

Internal refactoring only:

• Migrate to Yarn 2.
• Upgrade dependencies.

v1.5.0

• Reduces action run time from around 40 seconds to 1 second 🔥🚀. We now ship the packaged source with Vercel's ncc and run those directly rather than building on the fly with Docker.

v1.4.2

• Fixes #155. Thanks to @ui-valts-mazurs for reporting and fixing this one!

v1.4.1

• Fixes #145 (thanks @jnewland! 🤩).

v1.4.0

• Adds #119 (thanks @bryantbiggs! 🙏) the ability to configure whether changes are requested or not with on-failed-regex-request-changes. Existing behaviour is preserved.
• Upgrades all dependencies.

v1.3.0

• Adds #111, the ability to specify whether to create a review and whether to fail the action on a regex mismatch independently with on-failed-regex-fail-action & on-failed-regex-create-review.
• on-failed-regex-comment is no longer a required input.

Note: existing behaviour from previous releases is preserved without
additional configuration 🙏.