Skip to content

Conversation

@Mossaka
Copy link
Member

@Mossaka Mossaka commented Jan 13, 2026

Summary

This PR fixes the CI failures that have been affecting recent pull requests:

  • Fixed typo "Eeach" -> "Each" in crates/containerd-shim-wasmtime/README.md
  • Fixed typo "Bencharking" -> "Benchmarking" in docs/src/benchmarks.md
  • Fixed lifetime elision warning in RuntimeContext trait by explicitly specifying the lifetime parameter in entrypoint() method signature

Test plan

  • Verified spell check passes with typos
  • Verified doc tests pass with make test-doc
  • Verified wasmtime builds with make check-wasmtime

These changes resolve the spell check and rustdoc build failures observed in recent PRs such as #1062, #1060, and others.

🤖 Generated with Claude Code

This commit fixes the following CI failures:

1. Typo "Eeach" -> "Each" in crates/containerd-shim-wasmtime/README.md
2. Typo "Bencharking" -> "Benchmarking" in docs/src/benchmarks.md
3. Lifetime elision warning in RuntimeContext trait by explicitly
   specifying the lifetime parameter in entrypoint() method signature

These changes resolve the spell check and rustdoc build failures
observed in recent PRs.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Installing cross from git causes cargo to resolve dependencies to their
latest compatible versions. Some of these (like home v0.5.12+) require
rustc 1.88+, which is incompatible with the project's rustc 1.85.0.

Cross v0.2.5 from crates.io uses locked dependencies that support the
published MSRV of rustc 1.58.1+, making it compatible with rustc 1.85.0.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Mossaka and others added 4 commits January 13, 2026 22:36
mdbook 0.5.x requires rustc 1.88+, but the project uses rustc 1.85.0.
Pin mdbook to 0.4.52 (MSRV 1.82) and mdbook-mermaid to 0.16.0,
which are compatible with rustc 1.85.0.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
cargo install resolves dependencies to their latest compatible versions,
which can require newer Rust versions than the project's MSRV. For example,
the home crate v0.5.12+ requires rustc 1.88+, but the project uses 1.85.0.

Using cargo-binstall downloads pre-built binaries for cross, avoiding
dependency compilation entirely. This ensures compatibility with rustc 1.85.0.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
The Cross.toml was using the old string format for dockerfile paths:
  [target.TARGET]
  dockerfile = "path"

This prevented cross from passing required build args like CROSS_BASE_IMAGE,
CROSS_CMAKE_SYSTEM_PROCESSOR, and CROSS_SYSROOT to the Dockerfile.

Updated to the proper table format:
  [target.TARGET.dockerfile]
  file = "path"

This allows cross to automatically provide CROSS_BASE_IMAGE and other
environment variables that the Dockerfile expects.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
…s build args

The Dockerfile.musl expects CROSS_CMAKE_SYSTEM_PROCESSOR and CROSS_SYSROOT
to be set, but cross 0.2.5 doesn't automatically provide these variables
when using custom Dockerfiles.

Updated Cross.toml to explicitly pass these as build-args for musl targets:
- aarch64: CROSS_CMAKE_SYSTEM_PROCESSOR=aarch64, CROSS_SYSROOT=/usr/local/aarch64-linux-musl
- x86_64: CROSS_CMAKE_SYSTEM_PROCESSOR=x86_64, CROSS_SYSROOT=/usr/local/x86_64-linux-musl

Updated Dockerfile.musl to declare these as ARG so they can be passed in.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant