v1.21.1

Other Changes

• Fix static resource loading when Policy Bot's public URL contains path components (#260)

v1.21.0

Add support for enforcing regex rules on PR Title (#256)

Adds functionality for disapproving pull requests which do not comply by defined title formatting requirements as mentioned in #244.

• A new predicate title is added for defining allowed (not_match) and disallowed (match) regex patterns on a pull request title.
• The disapproval policy is extended to allow predicates just as individual approval_rules do. However, whereas an approval rule may only allow approvals subject to passing predicates, the disapproval policy will only allow disapprovals subject to its own predicates all failing. Passing predicates on the disapproval policy will trigger a default disapproval, just as failing predicates on an approval rule will implicitly approve (pass).

Add support for handling review comments (#257)

Adds support for handling review comments like regular comments, thus allowing users to approve or disapprove without switching back to the "Conversation" tab of the pull request whilst reviewing the changes. Fixes #51.

Other Changes

• Add documentation about referring to GitHub Apps in users fields (#255)
• Document UI development setup (#252)

v1.20.0

Improve reviewer assignment (#242)

Reviewer assignment now runs on all evaluations, meaning reviewers are correctly assigned when predicates change. Policy Bot will also re-request review if new approvals are needed after pushes. Otherwise, reviewers are requested once per rule and dismissed reviewers are not re-requested.

Add optional description field to rules (#251)

Approval rules can now have a description field that appears in the details UI when viewing the status of a pull request. Policies may use this field to explain what the rule is for or who needs to approve instead of putting this information in a long rule name.

Other Changes

• Reduce GitHub requests by skipping evaluation for webhook events that can't influence the result (#242)

v1.19.2

Add from_branch predicate (#243)

Policies can now use the from_branch predicate to enable rules based on the source (head) branch of a pull request.

Other Changes

• Load the app name from GitHub, ignoring the options.app_name server configuration property (#233)
• Fix post-login redirects in certain conditions (#238)

v1.17.2

Other Changes

• Fix author values for bot-authored pull requests (#231)

⚠️ Compatibility Note

This is the last policy-bot release to support GitHub Enterprise Server versions older than 2.21.0. Starting from policy-bot v1.18.0, GitHub Enterprise Server 2.21.0 or newer is required due to the use of new Team APIs.

v1.19.1

Other Changes

• Fix author values for bot-authored pull requests (#231)

v1.19.0

Add toggle to hide skipped rules in the UI (#228)

The pull request details view now has a toggle to hide skipped rules, making it easier to focus on the rules that actually apply in repositories with large numbers of rules.

Other Changes

• Fix file predicates so that they match both the old and new file paths in pull requests containing renames (#225)
• Upgrade TailwindCSS to 1.7.5 (#226)

v1.18.0

Use new API for team operations (#212)

Policy Bot now uses the new slug-based Team API to check and list team membership. This significantly reduces requests in organizations that have many teams.

⚠️ As a result of this change, Policy Bot now requires GitHub Enterprise Server 2.21.0+ or GitHub.com.

Other Changes

• Increase the maximum depth for approval rules (#220)

v1.17.1

Improve default Docker configuration (#211)

Published Docker images now include a default server configuration file. Additionally, configuration properties in the server block can be set using environment variables starting with POLICYBOT_. For example, the POLICYBOT_PUBLIC_URL variable now sets or overrides the server.public_url property.

Other Changes

• Fix label caching for pull request with no labels (#213)
• Only process review requests when it is enabled for at least one rule (#214)
• Use the v3 API to list repository collaborators, improving cross-request caching (#215)
• Upgrade palantir/go-githubapp to the latest version, introducing new error metrics and log fields (#216)

⚠️ Compatibility Note

This is the last policy-bot release to support GitHub Enterprise Server versions older than 2.21.0. Starting from policy-bot v1.18.0, GitHub Enterprise Server 2.21.0 or newer is required due to the use of new Team APIs.

v1.17.0

Other Changes

• Add GitHub client request timeout (#204)
• Upgrade google/go-github and palantir/go-githubapp to the latest versions (#204)