ci(release): drop the Intel Mac leg — macos-13 no longer schedules

.github/workflows/release.yml

@@ -31,8 +31,12 @@ jobs:
             os: ubuntu-latest
           - target: aarch64-apple-darwin
             os: macos-14
-          - target: x86_64-apple-darwin
-            os: macos-13
+          # No x86_64-apple-darwin leg: the `macos-13` runner label no longer
+          # gets picked up (a dry run sat queued indefinitely while the other
+          # three legs finished), and because `publish` needs every leg, that
+          # would hang the whole release rather than fail it. Intel Macs build
+          # from source — an aarch64 binary will not run there. Revisit if a
+          # supported Intel runner label reappears.
     steps:
       - uses: actions/checkout@v4
 

CLAUDE.md

@@ -2897,11 +2897,17 @@ branch on platform.
     `.github/workflows/ci.yml` runs `lint`/`test`/`plugins`/`wasm-e2e` as
     four independent jobs on every PR and `main` push, each routed through an
     existing `just` recipe (see the Development section above).
-    `.github/workflows/release.yml` builds four native targets
-    (`x86_64-unknown-linux-{gnu,musl}`, `{aarch64,x86_64}-apple-darwin`) on a
+    `.github/workflows/release.yml` builds three native targets
+    (`x86_64-unknown-linux-{gnu,musl}`, `aarch64-apple-darwin`) on a
     `v*` tag push and publishes a GitHub pre-release with a per-target
     tarball (binary + shell completions + README + LICENSE) plus a
-    `SHA256SUMS` file.
+    `SHA256SUMS` file. A `workflow_dispatch` trigger allows a dry run; the
+    publish step is gated on a real tag push so a dispatch builds and uploads
+    artifacts without creating a release. There is deliberately **no**
+    `x86_64-apple-darwin` leg — GitHub's `macos-13` label no longer picks up
+    jobs (a dry run sat queued indefinitely while the other legs finished),
+    and since `publish` declares `needs: build`, a never-scheduled leg would
+    hang the entire release rather than fail it.
 - Per-widget richer customization; naming the widget in the panic-guard `warn!`.
 - Range-on-binding — today a `run`/`open_url` click binding only fires on a
   widget that already emits a clickable range (i.e. has a non-empty

README.md

@@ -69,12 +69,15 @@ pane, window, host, and system info, with zero required configuration.
 
 ### Prebuilt release binary
 
-Each tagged release publishes prebuilt tarballs for four targets on GitHub:
+Each tagged release publishes prebuilt tarballs for three targets on GitHub:
 
 - `x86_64-unknown-linux-gnu`
 - `x86_64-unknown-linux-musl` (static; no glibc dependency)
 - `aarch64-apple-darwin` (Apple Silicon)
-- `x86_64-apple-darwin` (Intel Mac)
+
+There is no Intel Mac (`x86_64-apple-darwin`) build: GitHub's `macos-13` runner
+label no longer picks up jobs, and an Apple Silicon binary will not run on an
+Intel Mac. On an Intel Mac, [build from source](#build-from-source) instead.
 
 Each `rustline-<version>-<target>.tar.gz` contains the `rustline` binary,
 shell-completion scripts under `completions/` (`rustline.bash`, `_rustline`,