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)

v1.16.3

Other Changes

• Reduce requests when listing teams by using larger page sizes (#199)

v1.16.2

Other Changes

• Reduce requests when assigning reviewers by caching team and organization memberships (#195)
• Comment out development-only options in the example configuration file (#198)