Version 0.12.1

Fixes

1. Fixes issue linking behavior by using GitHub API instead of parsing the pull request body with regular expressions.

Version 0.12.0

Features

• Add verbose option that allows you to receive more verbose validation reports compared to the default behavior.

Other Changes

• Change the default reporting behavior. In all future releases, conventional-pr will only send messages whenever the validation fails. This will prevent noises caused by conventional-pr.
• Removes the report option. Validation reports will always logged in the action console.
• Renames template option to message.
• Renames maximum_file_changes option to maximum_changes
• Renames verified_commits option to signed.

Full Changelog: v0.11.0...v0.12.0

Version 0.11.0

Overview

This release adds the following features:

1. Add edit option to enable editing on the existing report with new data whenever a pull request validation is executed to reduce the amount of noise generated by the validation process. Do note that edit requires a personal access token with read:user scope and cannot be used with the GitHub Actions bot.

Version 0.10.1

Overview

This release fixes the following issue:

1. Changed the default label option to an empty string. This change is made to circumvent GitHub workflow limitations on forked repositories.
2. Changed emoji to constant strings in console reporter as it's easier to read and interpret.

Version 0.10.0

Overview

This release adds the following features:

• Add console reporting feature. Users can now opt-out from the standard pull request comment report and revert back to the old report mechanism on a standard console. This option is added to adhere GitHub workflow security limitations. Thanks @smutel for sharing their usecase!

Version 0.9.0

Overview

This release adds the following features:

1. Add username whitelist feature. Maintainers can now add a list of GitHub usernames to be whitelisted, so whenever those users submitted a pull request, the validation will be skipped. Thanks to @BinToss for sharing their use case!

Version 0.8.0

Overview

This release adds the following features:

1. Adds a new validator that enforces all commits in the branch to be signed. It's disabled by default. See why signed commits are important.
2. Use new workflow report formatting to improve whitelists' and validators' statuses. Users can now see whether a whitelist or validator is activated or not, rather than just getting a report whether the check passes or not. This also allows for better debugging.

Version 0.7.2

Overview

This release fixes the following bugs:

1. Subsequent pushes are not being validated #54. Now, every change on the target branch will be revalidated except when you told the workflow not to.

Additionally, the documentation has been updated to address the sub-events issues.

Kudos to @BinToss for filing this issue!

Version 0.7.1

Overview

This release fixes the GitHub Actions definition by replacing the required constraint for access_token to be true from an empty string which potentially will cause unwanted behavior.

Version 0.7.0

Overview

This release adds the following features:

1. Better error logging when the run fails. Now, it should be easier to debug the cause of the error (and it should reduce the amount of issues submitted to this repository) 🎉 .