fix(ci): standardize publish rust toolchain#4931
fix(ci): standardize publish rust toolchain#4931NathanFlurry wants to merge 2 commits into05-03-split_up_agentic_loop_testfrom
Conversation
PR #4931 Review: fix(ci): standardize publish rust toolchainState: CLOSED - reviewed for record. Overview This PR standardizes all publish Docker builds on Rust 1.91.1 and cleans up several dead-code warnings that would fail under Docker / Toolchain
CI Check Change (rust.yml)
Dead Code Fixes
VFS Metrics (depot-client/vfs.rs)
Guard-Core Tests Tests live in Envoy-Client Test Fixture
Summary
The core CI unblock is sound. The two items worth addressing before or after landing are the global |
Preview packages published to npmInstall with: npm install rivetkit@pr-4931All packages published as Engine binary is shipped via Docker images: docker pull rivetdev/engine:slim-883fbb7
docker pull rivetdev/engine:full-883fbb7Individual packagesnpm install rivetkit@pr-4931
npm install @rivetkit/react@pr-4931
npm install @rivetkit/rivetkit-napi@pr-4931
npm install @rivetkit/workflow-engine@pr-4931 |
ef9e36d to
e9cb881
Compare
7835a88 to
cb7241f
Compare
e9cb881 to
62e056d
Compare
62e056d to
2c95e97
Compare
a839e48 to
a9e01d7
Compare
e72d12a to
5c45e9b
Compare
|
Landed in main via stack-merge fast-forward push. Commits are in main; closing to match. |

What
Standardizes publish Docker builds on Rust 1.91.1 and keeps builder-base source Dockerfiles aligned. Also preserves the rustfmt/script-mode fixes from the failed CI run.
Why
Publish builders were split between rustc 1.89.0 and 1.91.0, while the locked AWS crates require rustc 1.91/1.91.1. Installing the same toolchain inside active publish build stages lets the current base images pass without waiting for a base-image rebuild.