Deploy Docs GitHub Action Failing since Nov 3 2025

[kfc35]

What went wrong

Expectation: Upon merges to main, Deploy Docs should run successfully.

Reality: Upon merges to main, it seems that every Deploy Docs run has been failing since November 3rd.

It fails with these last console messages:

error: the compiler unexpectedly panicked. this is a bug.

note: we would appreciate a bug report: https://github.com/rust-lang/rust/issues/new?labels=C-bug%2C+I-ICE%2C+T-rustdoc&template=ice.md

note: please make sure that you have updated to the latest nightly

note: please attach the file at `/home/runner/work/bevy/bevy/rustc-ice-2025-11-09T19_24_33-14036.txt` to your bug report

note: compiler flags: --crate-type lib -Z unstable-options -Z unstable-options

note: some of the compiler flags provided by cargo are hidden

query stack during panic:
end of query stack
error: could not document `bevy_camera`
warning: build failed, waiting for other jobs to finish...
Error: Process completed with exit code 101.

There is a stack trace printed before these; you can look at an individual run’s output to view more detail.

Additional information

GitHub Action located here: https://github.com/bevyengine/bevy/actions/workflows/docs.yml

The last successful run is this one: https://github.com/bevyengine/bevy/actions/runs/19046669974

Followed by two cancelled runs:
https://github.com/bevyengine/bevy/actions/runs/19046774657
https://github.com/bevyengine/bevy/actions/runs/19046844730

Then this is the first failed run in the current streak: https://github.com/bevyengine/bevy/actions/runs/19046890131

bevy_camera does seem to be touched by a commit from one of those aforementioned canceled runs, but I do not think it would result in this error.

[ekwoka]

The error suggests it's something in rustdoc that is the real bug, though maybe something about bevy could be adjusted.

It might not even be about bevy_camera, but something that causes the panic to hit at that package.

[kfc35]

It seems there’s another issue now with the Action failing introduced from:
https://github.com/bevyengine/bevy/actions/runs/20217497431/job/58032966778

error: failed to run custom build command for `x264-sys v0.2.2`

Caused by:
  process didn't exit successfully: `/home/runner/work/bevy/bevy/target/debug/build/x264-sys-3f80ca9695ce1873/build-script-build` (exit status: 101)
  --- stdout
  cargo:rerun-if-changed=/home/runner/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/x264-sys-0.2.2/Cargo.toml
  cargo:rerun-if-env-changed=X264_NO_PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR

  --- stderr

  thread 'main' (9456) panicked at /home/runner/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/x264-sys-0.2.2/build.rs:16:51:
  called `Result::unwrap()` on an `Err` value: PkgConfig(
  pkg-config exited with status code 1
  > PKG_CONFIG_ALLOW_SYSTEM_CFLAGS=1 pkg-config --libs --cflags x264 'x264 >= 0.147'

  The system library `x264` required by crate `x264-sys` was not found.
  The file `x264.pc` needs to be installed and the PKG_CONFIG_PATH environment variable must contain its parent directory.
  The PKG_CONFIG_PATH environment variable is not set.

  HINT: if you have installed the library, try setting PKG_CONFIG_PATH to the directory containing `x264.pc`.
  )
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish…

The commit in question (4eed4d0) did things with x264 so this seems to be a direct result of a code change