What problem does it solve? Bumping the pinned V8 / rusty_v8 version in a Rust project touches many files (Cargo.toml, Cargo.lock, MODULE.bazel, Bazel BUILD files, checksum manifests) and often breaks CI canary builds in non-obvious ways. This Skill provides a structured workflow to perform the version bump, validate the release-candidate path, and systematically diagnose failed V8 canary or artifact builds. ## Core Features & Use Cases - Guided Version Bump: Follows the release-process source of truth in third_party/v8/README.md and updates every surface carrying the pin, including sha256 manifests. - Checksum & Bazel Validation: Runs the rusty_v8_bazel.py helper scripts and their unit tests to keep MODULE.bazel checksums consistent. - Canary Validation: Checks the v8-canary CI result for the candidate branch or PR, falling back to an explicitly-labeled local substitute when CI is unavailable. - Failure Diagnosis: When builds fail, traces upstream deltas (binding layout, archive naming, GN/Bazel targets, libc++ inputs, stale patches) back into the Codex build graph and identifies the minimal fix. - Use Case: You need to move Codex to a new rusty_v8 release. The Skill walks you through updating the pins, validating via the v8-canary workflow, and—if the canary fails—pinpointing which upstream V8 change broke which Bazel file. ## Quick Start Use $update-v8-version to update Codex to the latest v8 release and validate the release-candidate path.
