Repository navigation
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #8058 +/- ##
==========================================
- Coverage 69.38% 69.38% -0.01%
==========================================
Files 696 696
Lines 181896 181896
Branches 29221 29221
==========================================
- Hits 126212 126209 -3
- Misses 38610 38613 +3
Partials 17074 17074 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
c37dbfc to
4c3bec9
Compare
6ceb0ef to
2da028e
Compare
1d5135d to
767610e
Compare
2da028e to
7c4c6e8
Compare
7c4c6e8 to
b51cac4
Compare
|
✅ Approved — The last review's WARNING (the Bazel crate lockfile wasn't regenerated) and its smaller notes are fixed at this commit, and there are no new issues. The decision is advisory: this comment never approves, blocks or requests changes on the pull request. ✅ All checks passed🔒 Security: ✅ LGTMThe helper fetches from fixed HTTPS URLs and passes 📖 AGENTS.md: ✅ LGTMNo AGENTS.md update is needed. 📋 Code Quality: ✅ LGTM
⚡ Performance: ✅ LGTMThis is an offline maintenance script and doesn't touch any hot path. 📝 Documentation: ✅ LGTMThe docs and the caret-compatibility comment now match the code. Reviewed commit: |
|
Since last review: 1 resolved, 0 still open, 2 new. Automates Chromium Rust dependency alignment, adds Bazel tests, and documents the V8 update workflow. Reviewed commit: 0accb61c · github run |
|
Instead of writing back to the Cargo.toml you could run |
b51cac4 to
0accb61
Compare
|
improved it... still needs one more round of deslopping imo |
V8 builds temporal_capi from Chromium's third_party/rust, at the revision pinned in V8's DEPS. Cargo resolves temporal_capi's tree within workerd's crate graph, so a crate can drift from the version Chromium builds V8 with. Following the RUST_ICU_MAJOR_VERSION_NUMBER update, which reads ICU's version at the commit pinned in V8's DEPS, read chromium_crates_io/Cargo.lock at V8's third_party/rust revision. Move the exact pins in deps/rust/Cargo.toml for crates in temporal_capi's runtime tree to Chromium's versions with one `cargo add`, which keeps their features, then move the remaining crates in Cargo.lock with `cargo update --precise`. If a crate still differs, fail and name it with Chromium's versions, since it needs an exact pin. Then regenerate deps/rust/cargo-bazel-lock.json with CARGO_BAZEL_REPIN, as build/deps/rust.MODULE.bazel requires after Cargo.toml or Cargo.lock changes. When Chromium locks several versions of a crate, the helper uses the one that is semver-compatible with workerd's, under Cargo's caret rules (including 0.0.x). Chromium's Cargo.lock and deps/rust/Cargo.toml are read with tomllib. `finish` runs this after the ICU update, and the new `rust-crates` command runs it for the current V8 version. //ci:v8_update_test covers the pin and lockfile moves, duplicate crate names in Chromium's lockfile, and the failure when Cargo refuses a version. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
0accb61 to
d797e6c
Compare
Applies to:
Kind of involved, but I think it's ok