1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
name: CI
# This file is byte-identical across all rs* repos. Do not edit it in one
# repo: edit the canonical copy in rsconstruct and sync it out. Everything
# repo-specific lives outside this file — scripts/ci-install-tools.sh installs
# the tools this repo's tests shell out to, and docs/ carries the mdBook.
# Branch pushes only, deliberately: `cargo release` pushes the release
# commit and its tag together, and an unfiltered `on: push` turned that
# into two identically-titled runs. The release pipeline runs from the
# default-branch push of the release commit (see is-release below); the
# tag push triggers nothing.
on:
push:
branches:
workflow_dispatch:
# Baseline is read-only; jobs that publish (release, docs) elevate their own
# permissions individually.
permissions:
contents: read
jobs:
test:
runs-on: ubuntu-26.04
timeout-minutes: 60
steps:
- name: Checkout
uses: actions/checkout@v6
with:
submodules: true
- name: Install Rust
uses: dtolnay/rust-toolchain@stable
with:
components: clippy
- name: Cache cargo registry and target
uses: Swatinem/rust-cache@v2
# Language runtimes come from the standard setup actions. Each installs
# into the runner's toolcache, which the runner user owns — so the
# install-tools script below can `pip install` / `npm install -g` /
# `gem install` with no venv, no GEM_HOME, no npm prefix, and no sudo.
- name: Set up Python
uses: actions/setup-python@v7
with:
python-version: '3.14'
- name: Set up Node
uses: actions/setup-node@v7
with:
node-version: '24'
- name: Set up Ruby
uses: ruby/setup-ruby@v1
with:
ruby-version: '3.3'
# Every repo owns scripts/ci-install-tools.sh: it installs the system
# libraries the build links against and the external tools the tests
# shell out to, and is an explicit no-op where there are none. It runs
# before the build because build scripts (e.g. -sys crates probing
# pkg-config) already need the libraries. The script is required — a
# repo without it fails here rather than silently skipping its setup.
# Nothing in the script may be best-effort: a tool that cannot be
# installed must fail this step instead of surfacing later as a
# confusing build or test failure.
- name: Install build and test tools
run: ./scripts/ci-install-tools.sh
- name: Build
run: cargo build
- name: Clippy
run: cargo clippy --all-targets -- -D warnings
# The suite hard-fails on any missing tool (tests never skip), so a
# gap in the tool setup fails the run loudly instead of shrinking it.
- name: Run tests
run: cargo test
build:
# is-release: a default-branch push of a `cargo release` commit
# ("chore: Release <crate> version <x.y.z>"). The tag itself does not
# trigger CI (see `on:` above), so the release commit's message is the
# release signal, and the tag name is recomputed from Cargo.toml —
# which the same commit bumped.
if: >-
github.event_name == 'push' &&
github.ref == format('refs/heads/{0}', github.event.repository.default_branch) &&
startsWith(github.event.head_commit.message, 'chore: Release ')
# A release never ships from a commit whose tests fail.
needs: test
# A newer release run supersedes any still-running one, even for a
# different version: the group ignores the ref, so a new release commit
# cancels the in-flight build of the same target from the previous one.
concurrency:
group: release-build-${{ matrix.target }}
cancel-in-progress: true
strategy:
matrix:
include:
- target: x86_64-unknown-linux-gnu
os: ubuntu-26.04
suffix: linux-x86_64
- target: aarch64-unknown-linux-gnu
os: ubuntu-26.04
suffix: linux-aarch64
- target: x86_64-apple-darwin
os: macos-latest
suffix: macos-x86_64
- target: aarch64-apple-darwin
os: macos-latest
suffix: macos-aarch64
runs-on: ${{ matrix.os }}
steps:
- name: Checkout
uses: actions/checkout@v6
with:
fetch-depth: 0
submodules: true
- name: Set artifact name
shell: bash
run: |
REPO="${{ github.event.repository.name }}"
echo "ARTIFACT=${REPO}-${{ matrix.suffix }}" >> "$GITHUB_ENV"
- name: Install Rust
uses: dtolnay/rust-toolchain@stable
with:
targets: ${{ matrix.target }}
- name: Cache cargo registry and target
uses: Swatinem/rust-cache@v2
with:
key: ${{ matrix.target }}
- name: Compute weekly apt cache key
if: runner.os == 'Linux'
run: echo "APT_CACHE_WEEK=$(date -u +%Y-W%V)" >> "$GITHUB_ENV"
- name: Cache apt archives
if: runner.os == 'Linux'
uses: actions/cache@v5
with:
path: ~/.cache/apt-archives
key: apt-${{ runner.os }}-${{ matrix.target }}-${{ env.APT_CACHE_WEEK }}
# Acquire::Retries because apt's default is 0: when the first mirror in
# /etc/apt/apt-mirrors.txt (azure.archive.ubuntu.com) is unreachable there
# is no second attempt. Retries=3 lets apt fall through to
# archive.ubuntu.com. No Timeout override and no timeout-minutes: a tight
# timeout killed the healthy-but-slow v0.9.56 release build at exactly
# 5 minutes (run 32261605657), which is worse than waiting out a slow
# mirror.
- name: Install cross-compilation tools (Linux aarch64)
if: matrix.target == 'aarch64-unknown-linux-gnu'
run: |
mkdir -p ~/.cache/apt-archives/partial
sudo apt-get -o Acquire::Retries=3 update
sudo apt-get -o Acquire::Retries=3 -o Dir::Cache::Archives="$HOME/.cache/apt-archives" install -y gcc-aarch64-linux-gnu
sudo chown -R "$USER" ~/.cache/apt-archives
- name: Build
env:
CARGO_TARGET_AARCH64_UNKNOWN_LINUX_GNU_LINKER: aarch64-linux-gnu-gcc
run: cargo build --release --target ${{ matrix.target }}
- name: Rename binary
run: cp target/${{ matrix.target }}/release/${{ github.event.repository.name }} ${{ env.ARTIFACT }}
- name: Upload artifact
uses: actions/upload-artifact@v7
with:
name: ${{ env.ARTIFACT }}
path: ${{ env.ARTIFACT }}
release:
# Same is-release condition as build (see the comment there).
if: >-
github.event_name == 'push' &&
github.ref == format('refs/heads/{0}', github.event.repository.default_branch) &&
startsWith(github.event.head_commit.message, 'chore: Release ')
needs: build
permissions:
contents: write
concurrency:
group: release-publish
cancel-in-progress: true
runs-on: ubuntu-26.04
steps:
# Checkout must precede the artifact download — it wipes the workspace.
# It is here only to read the released version out of Cargo.toml.
- name: Checkout
uses: actions/checkout@v6
- name: Download all artifacts
uses: actions/download-artifact@v8
with:
path: artifacts
merge-multiple: true
- name: Compute release tag from Cargo.toml
id: tag
run: |
set -euo pipefail
version="$(grep -m1 '^version' Cargo.toml | sed -E 's/.*"(.*)".*/\1/')"
echo "tag=v${version}" >> "$GITHUB_OUTPUT"
# `cargo release` pushes the signed tag alongside the commit, so by the
# time the cross-platform builds finish the tag exists and is used
# as-is; target_commitish only matters in the fallback where the tag
# push did not arrive and the action creates the tag itself.
- name: Create GitHub Release
uses: softprops/action-gh-release@v2
with:
tag_name: ${{ steps.tag.outputs.tag }}
target_commitish: ${{ github.sha }}
generate_release_notes: true
files: artifacts/*
docs:
# Deploys on a release (same is-release condition as build) or manually.
if: >-
github.event_name == 'workflow_dispatch' ||
(github.event_name == 'push' &&
github.ref == format('refs/heads/{0}', github.event.repository.default_branch) &&
startsWith(github.event.head_commit.message, 'chore: Release '))
needs: test
permissions:
contents: read
pages: write
id-token: write
concurrency:
group: pages
cancel-in-progress: true
environment:
name: github-pages
url: ${{ steps.deployment.outputs.page_url }}
runs-on: ubuntu-26.04
steps:
- name: Checkout
uses: actions/checkout@v6
with:
submodules: true
- name: Install mdBook
uses: peaceiris/actions-mdbook@v2
with:
mdbook-version: latest
- name: Populate release info page
run: |
set -euo pipefail
version="$(grep -m1 '^version' Cargo.toml | sed -E 's/.*"(.*)".*/\1/')"
# CI runs on the branch push, not the tag push, so the ref name is
# the branch; the tag is derived from the version the release
# commit put in Cargo.toml (cargo-release tags v<version>).
tag="v${version}"
commit="${GITHUB_SHA}"
released_at="$(date -u +'%Y-%m-%d %H:%M:%S UTC')"
run_url="${GITHUB_SERVER_URL}/${GITHUB_REPOSITORY}/actions/runs/${GITHUB_RUN_ID}"
file="docs/src/release-info.md"
sed -i \
-e "s|__VERSION__|${version}|g" \
-e "s|__GIT_TAG__|${tag}|g" \
-e "s|__GIT_COMMIT__|${commit}|g" \
-e "s|__RELEASE_DATE__|${released_at}|g" \
-e "s|__WORKFLOW_NAME__|${GITHUB_WORKFLOW}|g" \
-e "s|__WORKFLOW_RUN_NUMBER__|${GITHUB_RUN_NUMBER}|g" \
-e "s|__WORKFLOW_RUN_URL__|${run_url}|g" \
"${file}"
- name: Build book
run: mdbook build docs
- name: Upload artifact
uses: actions/upload-pages-artifact@v5
with:
path: docs/book
- name: Deploy to GitHub Pages
id: deployment
uses: actions/deploy-pages@v5