Releases: palantir/policy-bot
v1.17.0
v1.16.3
v1.16.2
v1.16.1
v1.16.0
Add teams
mode for reviewer requests (#183)
When using this mode, Policy Bot requests reviews from teams rather than individual users. The teams must be collaborators with at least read permissions on the repository.
Enable asynchronous processing for webhooks (#187)
Policy Bot now processes all webhooks in separate goroutines, avoiding issues with GitHub webhook delivery time outs. By default, there are 10 workers processing events with a queue size of 100. These values are adjustable using the workers.workers
and workers.queue_size
configuration properties.
Other Changes
1.15.1
Support check runs for has_successful_status
predicate (#176, #178)
Policy Bot now looks at statuses from check runs when evaluating the has_successful_status
predicate. This requires updating the app configuration in GitHub to grant read-only access to checks and enable check run webhooks.
Other Changes
- Update NPM development dependencies (#177)
1.15.0
Add ignore_commits_by
option (#156)
This option allows rules to ignore all commits that are authored and committed by users matching specific criteria. This can be useful to prevent automated commits from invalidating approval or to ignore changes by trusted contributors.
Add comment_patterns
approval method (#158)
This option takes a list of regular expressions that identify approval (and disapproval) comments. Use this method instead of the existing comments
method to match comments by exact text or by more complicated patterns.
Validate regular expressions when loading policies (#157)
Policies with invalid regular expressions now fail to load instead of failing only when a rule with an invalid expression is evaluated. Regular expressions are now also validated as part of the validation API.
Other Changes
1.14.0
Add has_labels
predicate (#151)
The has_labels
predicate makes approval rules conditional on the existence of labels on a pull request. All of the labels in the list must be present to activate the rule. This predicate is not recommended for security control given the relatively limited permissions required to add and remove labels.