-
Notifications
You must be signed in to change notification settings - Fork 3
274 lines (254 loc) · 11.9 KB
/
Copy pathpypi-publish.yml
File metadata and controls
274 lines (254 loc) · 11.9 KB
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
# Publish the `docling-rs` PyPI package (the PyO3 Python bindings in
# crates/docling-py) for a chosen release. Like the npm package, the bindings are
# a compiled native extension, so it can't be a one-line `twine upload`: a
# self-contained sdist is built first (maturin vendors the path-dependency
# crates), platform wheels are built from it on a matrix of runners (one abi3
# wheel per OS/arch — `abi3-py39`, so a single wheel covers every Python ≥ 3.9),
# and a publish job uploads the sdist + wheels to PyPI.
#
# Only allow-listed / GitHub-owned actions are used: the wheels are built with
# `pypa/cibuildwheel` (which orchestrates the manylinux containers and auditwheel
# repair itself) and uploaded with `pypa/gh-action-pypi-publish`.
#
# Trigger: manual only (workflow_dispatch), mirroring npm-publish.yml. By default
# it builds the checked-out ref at the current workspace version (the root
# Cargo.toml — same source npm-publish.yml uses), so the PyPI version tracks the
# crates automatically; pass `version` (or a release `tag`) to override. Run it
# from the Actions tab (or `gh workflow run pypi-publish.yml`, optionally
# `-f version=0.16.0`).
#
# No secrets: publishing uses PyPI Trusted Publishing (OIDC), like
# docling-core's pypi.yml. This requires a one-time setup on PyPI — add a trusted
# publisher for the `docling-rs` project pointing at this repo, workflow file
# (`pypi-publish.yml`) and environment (`pypi`). GitHub then mints a short-lived
# OIDC token per run; there is no API token to store or rotate.
#
# The ONNX Runtime is statically bundled at build time (`ort` `download-binaries`)
# and pdfium is loaded at runtime from the model cache, so the wheels are
# self-contained for the declarative path and need no extra native setup here —
# same story as the npm build.
name: pypi publish
on:
workflow_dispatch:
inputs:
tag:
description: "Release tag to build (e.g. v0.16.0). Blank = current ref."
required: false
default: ""
version:
description: "Override the PyPI version (e.g. 0.16.0). Blank = tag, or workspace version from the root Cargo.toml."
required: false
default: ""
cuda_wheel:
description: "Also build the docling-rs-cuda wheel (Linux x86_64, CUDA EP compiled in)."
required: false
type: boolean
default: false
concurrency:
group: pypi-publish-${{ inputs.tag || github.ref }}
cancel-in-progress: false
permissions:
contents: read
jobs:
sdist:
name: sdist
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with:
ref: ${{ inputs.tag || github.ref }}
# Version resolution mirrors npm-publish.yml: explicit `version` input,
# else the release `tag`, else the workspace version from the root
# Cargo.toml (NOT pyproject.toml — the version committed there is a
# local-build fallback that release.sh never bumps). The resolved version
# is always patched into [project].version before the sdist is built so
# every wheel (built from the sdist) inherits it.
- name: Resolve version
shell: bash
working-directory: crates/docling-py
run: |
v="${{ inputs.version }}"
if [ -z "$v" ] && [ -n "${{ inputs.tag }}" ]; then v="${{ inputs.tag }}"; v="${v#v}"; fi
if [ -z "$v" ]; then
v="$(grep -m1 '^version = ' ../../Cargo.toml | sed -E 's/.*"([^"]+)".*/\1/')"
fi
sed -i.bak -E "0,/^version = \".*\"/s//version = \"$v\"/" pyproject.toml && rm -f pyproject.toml.bak
echo "Building docling-rs $v"
- uses: actions/setup-python@v5
with:
python-version: "3.11"
# A maturin sdist vendors docling-py's path-dependency crates (docling,
# docling-core, docling-pdf, docling-asr) into a self-contained tarball that
# builds from source with a plain `pip install` — the input cibuildwheel
# unpacks for the per-platform wheels.
- name: Build sdist
run: |
python -m pip install "maturin>=1.5,<2"
maturin sdist -m crates/docling-py/Cargo.toml --out dist
- uses: actions/upload-artifact@v4
with:
name: sdist
path: dist/*.tar.gz
if-no-files-found: error
wheels:
name: wheel ${{ matrix.arch }}
needs: sdist
runs-on: ${{ matrix.host }}
strategy:
fail-fast: false
matrix:
include:
- host: ubuntu-22.04
arch: x86_64
# Native ARM64 Linux runner — avoids QEMU / cross-compiling the ONNX build.
- host: ubuntu-24.04-arm
arch: aarch64
- host: windows-latest
arch: AMD64
# macOS wheels are omitted: GitHub-hosted macOS runners are blocked in
# this environment. macOS users install the sdist (builds from source).
steps:
- name: Download sdist
uses: actions/download-artifact@v4
with:
name: sdist
path: sdist
# Unpack the self-contained sdist to a fixed dir for cibuildwheel to build.
- name: Unpack sdist
shell: bash
run: |
mkdir pkg
tar -xzf sdist/*.tar.gz -C pkg --strip-components=1
- name: Build wheels
uses: pypa/cibuildwheel@v2.21.3
with:
package-dir: pkg
output-dir: wheelhouse
env:
# abi3-py39 → build once (on cp39); the wheel covers every Python ≥ 3.9.
CIBW_BUILD: "cp39-*"
CIBW_ARCHS: ${{ matrix.arch }}
# `ort`'s `download-binaries` ships ONNX Runtime only for glibc targets,
# not musl — so build manylinux wheels only, never musllinux.
CIBW_SKIP: "*-musllinux*"
# Broad-compat Linux wheels; ONNX is statically linked so no repair pulls.
CIBW_MANYLINUX_X86_64_IMAGE: manylinux_2_28
CIBW_MANYLINUX_AARCH64_IMAGE: manylinux_2_28
# The manylinux containers have no Rust — install the toolchain once per
# container and put cargo on PATH for the maturin build.
CIBW_BEFORE_ALL_LINUX: "curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y --profile minimal --default-toolchain stable"
CIBW_ENVIRONMENT_LINUX: 'PATH="$HOME/.cargo/bin:$PATH"'
- uses: actions/upload-artifact@v4
with:
name: wheel-${{ matrix.arch }}
path: wheelhouse/*.whl
if-no-files-found: error
# CUDA wheel (PyPI `docling-rs-cuda`): the same sdist built with
# `--features cuda`, Linux x86_64 only — the renamed package installs the
# same `docling_rs` module (mutually exclusive with `docling-rs`) and
# defaults to `auto`: GPU when usable, CPU fallback (`DOCLING_RS_EP=cpu`
# forces CPU).
# Operational notes:
# - the wheel bundles libonnxruntime_providers_{shared,cuda}.so; if PyPI
# rejects the upload for size, request a per-project file-size bump
# (onnxruntime-gpu is the precedent). CUDA 12 + cuDNN 9 remain *system*
# requirements at runtime — the wheel does not ship them.
# - PyPI Trusted Publishing is per-project: register this workflow as a
# trusted publisher on the `docling-rs-cuda` project as well, or the
# publish step will reject that wheel.
# - NOT built in a manylinux_2_28 container like the CPU wheels: the pyke
# CUDA ONNX Runtime static binaries need glibc >= 2.38 (__isoc23_*
# symbols), so linking in a 2.28 container fails. Building on plain
# ubuntu-24.04 (glibc 2.39) works and maturin's audit tags the wheel
# manylinux_2_38 — i.e. the wheel requires Ubuntu 24.04+/Debian 13+ era
# glibc at runtime, which matches the native `--features cuda` story.
wheel-cuda:
name: wheel x86_64 (docling-rs-cuda)
if: inputs.cuda_wheel
needs: sdist
runs-on: ubuntu-24.04
steps:
- name: Download sdist
uses: actions/download-artifact@v4
with:
name: sdist
path: sdist
- name: Unpack sdist
run: |
mkdir pkg
tar -xzf sdist/*.tar.gz -C pkg --strip-components=1
- name: Install Rust (stable)
run: |
rustup toolchain install stable --profile minimal
rustup default stable
- name: Build docling-rs-cuda wheel
run: |
python3 -m pip install --user "maturin>=1.5,<2"
cd pkg
sed -i 's/^name = "docling-rs"$/name = "docling-rs-cuda"/' pyproject.toml
# Where the crate manifest sits depends on the maturin that built the
# sdist: at the root (older layouts) or in a subdirectory pointed at
# by [tool.maturin] manifest-path (1.8+ vendors the path-dependency
# crates as siblings — e.g. docling-py/Cargo.toml). Resolve it from
# pyproject.toml instead of assuming, and let cargo report the
# matching target directory (the crate is its own workspace, so it
# is NOT ./target when the manifest moved).
MANIFEST="$(python3 -c 'import tomllib; print(tomllib.load(open("pyproject.toml","rb"))["tool"]["maturin"].get("manifest-path", "Cargo.toml"))')"
TARGET_DIR="$(cargo metadata --no-deps --format-version 1 --manifest-path "$MANIFEST" | python3 -c 'import json, sys; print(json.load(sys.stdin)["target_directory"])')"
# ONNX Runtime dlopens the provider libraries by bare name; give the
# native module an $ORIGIN rpath so the copies shipped inside the
# wheel are found without any environment setup.
export RUSTFLAGS='-C link-arg=-Wl,-rpath,$ORIGIN'
# Build once so ort fetches the CUDA ONNX Runtime and copy-dylibs
# drops the provider libraries next to <target>/release...
cargo build --release --features cuda --manifest-path "$MANIFEST"
cp "$TARGET_DIR/release/libonnxruntime_providers_shared.so" \
"$TARGET_DIR/release/libonnxruntime_providers_cuda.so" \
python/docling_rs/
# ...then assemble the wheel (cargo cache is warm) with the provider
# libraries riding along as package data (pyproject include glob).
# The wheel MUST contain them — fail the job if the glob missed.
python3 -m maturin build --release --features cuda --out ../wheelhouse
python3 - <<'EOF'
import glob, sys, zipfile
wheel = glob.glob("../wheelhouse/*.whl")[0]
names = zipfile.ZipFile(wheel).namelist()
want = ["docling_rs/libonnxruntime_providers_shared.so",
"docling_rs/libonnxruntime_providers_cuda.so"]
missing = [w for w in want if w not in names]
sys.exit(f"provider libs missing from {wheel}: {missing}" if missing else 0)
EOF
- uses: actions/upload-artifact@v4
with:
name: wheel-cuda
path: wheelhouse/*.whl
if-no-files-found: error
publish:
name: publish to PyPI
needs: [sdist, wheels, wheel-cuda]
# wheel-cuda is optional (gated on the cuda_wheel input): publish when it
# succeeded or was skipped, never when anything actually failed.
if: ${{ !cancelled() && needs.sdist.result == 'success' && needs.wheels.result == 'success' && (needs.wheel-cuda.result == 'success' || needs.wheel-cuda.result == 'skipped') }}
runs-on: ubuntu-latest
# Trusted Publishing (OIDC): no token secret. `id-token: write` lets the job
# mint the OIDC token PyPI verifies against its trusted-publisher config; the
# `pypi` environment name is part of what PyPI matches on.
environment:
name: pypi
url: https://pypi.org/p/docling-rs
permissions:
id-token: write
steps:
# All wheels + the sdist → a single dist/ for the upload.
- name: Download artifacts
uses: actions/download-artifact@v4
with:
path: dist
merge-multiple: true
- name: Publish to PyPI
uses: pypa/gh-action-pypi-publish@release/v1
with:
packages-dir: dist
attestations: true
# Idempotent re-runs: don't fail if a version is already uploaded.
skip-existing: true