Releases: palantir/policy-bot
v1.23.3
v1.23.2
v1.23.1
v1.23.0
Add support for shared organization policies (#321)
Refactor configuration loading to use the go-githubapp/appconfig
package. This mostly adds support for shared organization policies (in the .github
repository by default), but should also make error messages more accurate.
It also changes the policy link in the details view to point to the resolved policy, instead of the local policy file.
Other Changes
- Update google/go-github to v38 (#326)
- Upgrade build dependencies
v1.22.1
v1.22.0
Add signature verification predicates (#285)
Policies can now use the has_valid_signatures
, has_valid_signatures_by
, and has_valid_signatures_by_key
to enable rules based on the GPG signatures of commits in the pull requests.
Add support for triage
and maintain
permissions (#294)
Policies can use the requires.permissions
option to specify the minimum permission a collaborator must have to approve a rule. This option replaces the existing admins
and write_collaborators
options, which are now deprecated.
As a result of this change, policies that still use the admins
and write_collaborators
options will behave slightly differently:
- Rules that set
write_collaborators: true
can also be approved by users withmaintain
andadmin
permissions - Rules that set
admins: true
and enable review requests will now request direct admins in addition members of admin teams
Other Changes
v1.21.4
v1.21.3
Avoid updating state on closed PRs (#270)
- Skips updating the status check for evaluations on pull requests that are not in an "open" state. This will avoid the situation where policy-bot attempts to update the status for a PR which has been closed/merged, causing errors or confusion if successful.
Other Changes
v1.21.2
Update status check on details page evaluation (#265)
- When the detail page is opened and evaluation is run the status check will now be updated. This resolves a class of issues where the triggered evaluation fails due to a temporary error, yet loading the details page results in a success message once the error is resolved (and the failed status check remains).
- Increased detail in logging around missing commits error message.