Build failed. If you want to re-trigger a documentation build, you can do it here. You can find more information on docs.rs builds documentation on the builds page.
# error kind ExecutionFailed
# pre-build errors command failed: exit status: 101
# rustc version rustc 1.99.0-nightly (d0babd8b6 2026-07-15)
# docs.rs version docsrs 0.0.0 (f1b150f0cd76f7cabcd39e1f4790ba771b28b5c4 2026-07-19 )
# build log [INFO] running `Command { std: "docker" "exec" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "DOCS_RS=1" "-w" "/opt/rustwide/workdir" "--user" "1001:1001" "45bc191e3b3c0b8a6296cc9fe3578fea9d37c778acad81264d03f3282578febb" "/opt/rustwide/cargo-home/bin/cargo" "+nightly-2026-07-16" "rustdoc" "--lib" "-Zrustdoc-map" "--config" "build.rustdocflags=[\"--cfg\", \"docsrs\", \"-Z\", \"unstable-options\", \"--emit=html-non-static-files\", \"--resource-suffix\", \"-20260715-1.99.0-nightly-d0babd8b6\", \"--static-root-path\", \"/-/rustdoc.static/\", \"--cap-lints\", \"warn\", \"--extern-html-root-takes-precedence\"]" "--offline" "-Zunstable-options" "--config=doc.extern-map.registries.crates-io=\"https://docs.rs/{pkg_name}/{version}/x86_64-unknown-linux-gnu\"" "-Zrustdoc-scrape-examples" "-j6" "--target" "x86_64-unknown-linux-gnu", kill_on_drop: false }` [INFO] [stderr] warning: target filter specified, but no targets matched; this is a no-op [INFO] [stderr] Checking zerovec v0.11.6 [INFO] [stderr] Checking zerotrie v0.2.4 [INFO] [stderr] Compiling pyo3-ffi v0.20.3 [INFO] [stderr] Compiling heck v0.4.1 [INFO] [stderr] Compiling serde v1.0.229 [INFO] [stderr] Compiling portable-atomic v1.14.0 [INFO] [stderr] error: failed to run custom build command for `pyo3-ffi v0.20.3` [INFO] [stderr] [INFO] [stderr] Caused by: [INFO] [stderr] process didn't exit successfully: `/opt/rustwide/target/debug/build/pyo3-ffi-d94d61a52fb49abf/build-script-build` (exit status: 1) [INFO] [stderr] --- stdout [INFO] [stderr] cargo:rerun-if-env-changed=PYO3_CROSS [INFO] [stderr] cargo:rerun-if-env-changed=PYO3_CROSS_LIB_DIR [INFO] [stderr] cargo:rerun-if-env-changed=PYO3_CROSS_PYTHON_VERSION [INFO] [stderr] cargo:rerun-if-env-changed=PYO3_CROSS_PYTHON_IMPLEMENTATION [INFO] [stderr] cargo:rerun-if-env-changed=PYO3_PRINT_CONFIG [INFO] [stderr] cargo:rerun-if-env-changed=PYO3_USE_ABI3_FORWARD_COMPATIBILITY [INFO] [stderr] [INFO] [stderr] --- stderr [INFO] [stderr] error: the configured Python interpreter version (3.14) is newer than PyO3's maximum supported version (3.12) [INFO] [stderr] = help: please check if an updated version of PyO3 is available. Current version: 0.20.3 [INFO] [stderr] = help: set PYO3_USE_ABI3_FORWARD_COMPATIBILITY=1 to suppress this check and build anyway using the stable ABI [INFO] [stderr] warning: build failed, waiting for other jobs to finish... [INFO] running `Command { std: "docker" "inspect" "45bc191e3b3c0b8a6296cc9fe3578fea9d37c778acad81264d03f3282578febb", kill_on_drop: false }`