You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`brew install` fails with an opaque `sandbox-exec ... build.rb exited with 1` backtrace | Homebrew 6+ refuses to load formulae from untrusted taps; the real warning scrolls past before the error. Run `brew trust doitintl/dci-cli` and retry. |
85
+
|`brew install` fails with an opaque `sandbox-exec ... build.rb exited with 1` backtrace |A Homebrew 6.0.0–6.0.1 bug blocked installs from third-party taps. Run `brew update` to get 6.0.2+ (which auto-trusts fully-qualified installs) and retry. |
86
86
|`release.yml` stuck queued | Another release for the same tag is in progress — wait or cancel it |
87
87
| WinGet PR submission skipped |`WINGET_GH_PAT` secret is not configured — add a PAT with `public_repo` scope |
@@ -99,4 +99,3 @@ To re-release: fix the issue, tag a new patch version, and push.
99
99
-**Windows ARM64** is excluded due to a missing cross-compiler in `goreleaser-cross` ([goreleaser-cross#117](https://github.com/goreleaser/goreleaser-cross/issues/117)).
100
100
-**WinGet** submissions are automated via `sync-manifests.yml`, which opens a PR to [microsoft/winget-pkgs](https://github.com/microsoft/winget-pkgs) on each release. This requires a `WINGET_GH_PAT` secret (a GitHub PAT with `public_repo` scope) and a fork of `winget-pkgs` (currently `apgiorgi/winget-pkgs`). Microsoft's automated validation runs on each PR — approval is typically within hours.
101
101
-**Homebrew tap** relies on a GitHub redirect from `doitintl/homebrew-dci-cli` to this repo. Do not create a repo named `homebrew-dci-cli` in the org.
102
-
-**Homebrew 6 tap trust**: because of the redirect above, Homebrew records the tap with a non-canonical remote (`github.com/doitintl/dci-cli` instead of the `homebrew-dci-cli` URL implied by the tap name). Homebrew treats such taps as "custom remote" and disables both per-formula trust and the auto-trust normally granted by fully-qualified installs — so `brew install doitintl/dci-cli/dci` alone fails on Homebrew 6+, and users must run `brew trust doitintl/dci-cli` (whole-tap trust) first. Creating a real `homebrew-dci-cli` tap repo would restore canonical-remote behavior, at the cost of maintaining a second repo.
Copy file name to clipboardExpand all lines: README.md
+1-4Lines changed: 1 addition & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,8 +7,7 @@
7
7
## Installation
8
8
9
9
```bash
10
-
# macOS (Homebrew) — the `brew trust` step is required once on Homebrew 6+
11
-
brew trust doitintl/dci-cli
10
+
# macOS (Homebrew)
12
11
brew install doitintl/dci-cli/dci
13
12
14
13
# Windows (WinGet)
@@ -133,8 +132,6 @@ winget upgrade DoiT.dci
133
132
scoop update dci
134
133
```
135
134
136
-
> **Note (Homebrew 6+):** if `dci` stops appearing in `brew upgrade`, the tap is untrusted and Homebrew skips it silently. Run `brew trust doitintl/dci-cli` once to fix it.
137
-
138
135
## Authentication
139
136
140
137
By default, `dci` authenticates interactively via the DoiT Console (OAuth). For CI pipelines and non-interactive environments, set the `DCI_API_KEY` environment variable:
0 commit comments