|
1 | 1 | ---
|
2 |
| -last_review_date: "2025-06-16" |
| 2 | +last_review_date: "2025-08-06" |
3 | 3 | ---
|
4 | 4 |
|
5 | 5 | # Autobump
|
6 | 6 |
|
7 |
| -[BrewTestBot](BrewTestBot.md) automatically checks for available updates of packages that are in Homebrew's "autobump list" for official repositories. These packages should not have to be bumped (i.e versions increased) manually by a contributor. Instead, every 3 hours a GitHub Action opens a new pull request to upgrade to the latest version of a formula/cask, if needed. |
| 7 | +In official repositories, [BrewTestBot](BrewTestBot.md) automatically checks for available updates to packages that are in Homebrew's "autobump list". These packages do not need to be bumped (i.e. have their version number increased) manually by a contributor. Instead, every 3 hours, a GitHub Action opens a new pull request to upgrade them to the latest version, if needed. |
8 | 8 |
|
9 | 9 | ## Excluding packages from autobumping
|
10 | 10 |
|
11 |
| -By default, all new formulae and casks from [Homebrew/core](https://github.com/Homebrew/homebrew-core) and [Homebrew/cask](https://github.com/Homebrew/homebrew-cask) repositories are autobumped. To exclude a package from being autobumped, it must: |
| 11 | +By default, all new formulae and casks from the [Homebrew/core](https://github.com/Homebrew/homebrew-core) and [Homebrew/cask](https://github.com/Homebrew/homebrew-cask) repositories are autobumped. To exclude a package from the autobump list, it must have one of the following: |
12 | 12 |
|
13 |
| -1. have a `deprecate!` or `disable!` call |
14 |
| -2. have a `livecheck do` block containing a `skip` call |
15 |
| -3. has no `no_autobump!` call |
| 13 | +* an active `deprecate!` or `disable!` call |
| 14 | +* a `livecheck do` block containing a `skip` call |
| 15 | +* a `no_autobump!` call |
16 | 16 |
|
17 |
| -There are other formula or cask-specific reasons listed in the Formula Cookbook and Cask Cookbook respectively. |
| 17 | +Other formula and cask specific reasons for why a package is not autobumped are listed in the [Formula Cookbook](Formula-Cookbook.md) and [Cask Cookbook](Cask-Cookbook.md) respectively. |
18 | 18 |
|
19 |
| -To use `no_autobump!`, a reason for exclusion must be provided. We prefer use of one of the supported symbols. These can be found in the [`NO_AUTOBUMP_REASONS_LIST`](https://rubydoc.brew.sh/top-level-namespace.html#NO_AUTOBUMP_REASONS_LIST-constant). |
| 19 | +## Autobump exclusion reasons |
20 | 20 |
|
21 |
| -The reasons can be specified by their symbols: |
| 21 | +When using `no_autobump!`, a reason for exclusion must be provided. |
| 22 | + |
| 23 | +There are two ways to indicate the reason. The preferred way is to use a pre-existing symbol, which can be found in [`NO_AUTOBUMP_REASONS_LIST`](https://rubydoc.brew.sh/top-level-namespace.html#NO_AUTOBUMP_REASONS_LIST-constant), for example: |
22 | 24 |
|
23 | 25 | ```ruby
|
24 | 26 | no_autobump! because: :bumped_by_upstream
|
25 | 27 | ```
|
26 | 28 |
|
27 |
| -If none of the existing reasons fit, a custom reason can be provided as a string: |
| 29 | +If these pre-existing reasons do not fit, a custom reason can be specified: |
28 | 30 |
|
29 | 31 | ```ruby
|
30 | 32 | no_autobump! because: "some unique reason"
|
31 | 33 | ```
|
32 | 34 |
|
33 |
| -If there are multiple packages with a similar custom reason, it be added to `NO_AUTOBUMP_REASONS_LIST`. |
| 35 | +If there are multiple packages with a similar custom reason, it can be added as a new symbol to `NO_AUTOBUMP_REASONS_LIST`. |
0 commit comments