update-v8-version
Update Codex's pinned `v8` / `rusty_v8` versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds. Use when asked to bump V8, update `rusty_v8` artifacts, prepare or validate a V8 release candidate, check `v8-canary`, or diagnose why a V8 version update no longer builds.
Install
git clone https://github.com/openai/codex /tmp/codex && ln -s /tmp/codex/.codex/skills/update-v8-version ~/.claude/skills/update-v8-versionFrom README
Update V8 Version Core Workflow Read thirdparty/v8/README.md and follow its version-bump sequence. Treat that document as the release-process source of truth. Inspect and update the concrete repo surfaces that carry the pin: codex-rs/Cargo.toml codex-rs/Cargo.lock MODULE.bazel thirdparty/v8/BUILD.bazel thirdparty/v8/README.md the matching thirdparty/v8/rustyv8 .sha256 manifest when the remaining prebuilt inputs change Keep the existing checksum helpers in the loop: Validate the release-candidate path before broadening the work: Prefer checking the v8-canary CI result for the candidate branch or PR when one exists, using GitHub check tooling or gh as appropriate. If CI is unavailable or the user asked for a local-only check, run the closest local validation that is practical for the changed surface and say explicitly that it is a local substitute, not the full hosted canary. If the canary path passes, stop there.