From 41daf100284c91a6e6df3697017a4ac8835d50cc Mon Sep 17 00:00:00 2001 From: Channing Conger Date: Mon, 11 May 2026 22:48:33 +0000 Subject: [PATCH] docs(v8): document release update workflow --- third_party/v8/README.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/third_party/v8/README.md b/third_party/v8/README.md index ff98674140..336d03c74b 100644 --- a/third_party/v8/README.md +++ b/third_party/v8/README.md @@ -23,6 +23,18 @@ Current pinned versions: - Rust crate: `v8 = =147.4.0` - Embedded upstream V8 source for Bazel-produced release builds: `14.7.173.20` +## Updating to a new `v8` release + +Use this as the maintainer flow for a version bump: + +1. Bump the `v8` crate version and refresh `codex-rs/Cargo.lock`. +2. Update the Bazel versioned inputs in `MODULE.bazel`, then refresh the + matching checksum manifest and generated checksums as described below. +3. Publish a release-candidate PR and validate that `v8-canary` passes. +4. If the canary is green, publish the release tag and release build. +5. Once the release build completes, rerun the build on the candidate branch + and verify that the final artifact builds and tests pass. + When changing the remaining prebuilt `rusty_v8` `http_file` inputs, keep the checked-in checksum manifest and `MODULE.bazel` in sync: