Skip to content

Releases: palantir/bulldozer

v1.13.0

15 Apr 20:32
19a4b08
Compare
Choose a tag to compare

Update pull requests on more events (#235)

Pull requests that match trigger conditions for updates are now updated when they are opened or when labels are added. Previously, pull requests only updated if the target branch changed after the pull request was opened.

Other Changes

  • Users may customize the environment variable prefix by setting the BULLDOZER_ENV_PREFIX variable (#229)
  • Build with Go 1.16.3 (#237)
  • Remove Bintray publishing and move binary distributions to GitHub Releases (#234, #237)
  • Use GitHub Actions for CI (#237)

v1.12.0

18 Mar 22:23
c27b66a
Compare
Choose a tag to compare

Fix handling of skipped and neutral check results (#223)

Bulldozer now accepts skipped and neutral checks as valid conclusions for required statuses, matching GitHub's behavior. This applies both for required statuses set by branch protection and required statuses set in the Bulldozer configuration file.

Other Changes

  • Support setting server configuration, such as the listen address and port, with environment variables (#220)
  • Upgrade palantir/go-baseapp to 0.2.3 (#228)
  • Enable CodeQL vulnerability scanning (#221)

v1.11.0

27 Jan 22:07
923a21e
Compare
Choose a tag to compare

Add option to prevent merges without required checks (#217)

By default, Bulldozer will now avoid merging pull requests that target branches with no required status checks.

To continue using the previous behavior, set the merge.allow_merge_with_no_checks option to true like so:

version: 1

merge:
  allow_merge_with_no_checks: true

The v0 configuration format is not updated to support this feature. Repositories using the v0 configuration will be treated as if allow_merge_with_no_checks is set to the default value false.

v1.10.1

28 Sep 16:54
a495289
Compare
Choose a tag to compare

Add branch_patterns trigger condition (#200)

Users can now set the branch_patterns option to a list of regular expressions to trigger merges to branches with names that match any of the patterns.

Other Changes

  • Fix regression (from 1.9.0) with the body: empty_body option for squash commits (#193)
  • Upgrade palantir/go-githubapp to the latest version, introducing new error metrics and log fields (#201)

v1.10.0

28 Jul 16:44
88d5aed
Compare
Choose a tag to compare

Replace use of whitelist/blacklist with trigger/ignore (#196)

Users can now specify trigger and ignore instead of whitelist
and blacklist in their configuration options, respectively.

The blacklist and whitelist options are deprecated and will
be removed in a future release.

Account for special GitHub behavior with Travis CI (#194)

Travis CI status checks are apparently special-cased in GitHub code for
protected branches such that they behave differently from all other
checks. To allow Bulldozer to work for users of Travis CI Enterprise,
implement a matching special case in Bulldozer.

v1.9.1

12 Jun 18:08
dacb4cd
Compare
Choose a tag to compare

Other Changes

  • Include a default configuration file in the Docker image (#189). Note that this file does not set certain required properties that must be set using environment variables or by mounting your own configuration file.

v1.9.0

28 Apr 17:16
9f4be40
Compare
Choose a tag to compare

Improve asynchronous processing for webhooks (#180)

While Bulldozer previously performed merges and updates in separate goroutines, this release moves all webhook processing out of the request handler goroutine. By default, there are 10 workers processing events with a queue size of 100. These values can be adjusted using the workers.workers and workers.queue_size configuration properties.

Other Changes

  • Update google/go-github, palantir/go-githubapp, and palantir/go-baseapp to the latest versions (#179)
  • Convert to Go modules. Version tags will have a leading v going forward but published versions will be the same as before. (#179)
  • Improve the example server configuration file (#182)

1.8.0

07 Apr 21:23
7d497e1
Compare
Choose a tag to compare

Add support for fast-forward merging (#176)

Using the new merge mode ff-only will fast-forward the target branch of the pull request to match the source branch. This merge method only works if a fast-forward merge is possible, i.e. the source branch contains all commits on the target branch.

Other Changes

  • Clarify when push_restriction_user_token is required in response to GitHub updates (#171)

1.7.2

27 Feb 10:44
bd5c607
Compare
Choose a tag to compare

Other Changes

  • Add additional debug logging around evaluation and signals (#168)
  • Update google/go-github to the latest version, skipping webhook payload validation when the secret is empty (#167)

1.7.1

19 Nov 18:33
Compare
Choose a tag to compare

Other Changes

  • Upgrade palantir/go-githubapp, fixing a rare panic in GitHub client middleware (#152, #162)
  • Build with Go 1.13.4 (#159)