update-v8-version

Updates pinned v8 and rusty_v8 versions and validates release-candidate builds.

5|1|Updated Jun 26, 2026
One-click install
npx skills add https://github.com/looooonk/better-codex --skill update-v8-version-looooonk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-v8-version
Source: https://github.com/looooonk/better-codex/tree/main/.codex/skills/update-v8-version
Command: npx skills add https://github.com/looooonk/better-codex --skill update-v8-version-looooonk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Bumping the pinned V8 / rusty_v8 version in a Rust project touches many files (Cargo manifests, Bazel modules, checksum manifests) and often breaks CI builds, making manual updates error-prone and hard to validate. ## Core Features & Use Cases - Guided Version Bumps: Follows the documented release process to update Cargo.toml, Cargo.lock, MODULE.bazel, BUILD.bazel, and the rusty_v8_<version>.sha256 manifest consistently. - Release-Candidate Validation: Checks the v8-canary CI workflow for the candidate branch, or runs the closest local validation when CI is unavailable. - Failure Diagnosis: When canary builds fail, traces upstream deltas in denoland/rusty_v8 and V8 (binding layout, archive naming, GN/Bazel targets, stale patches) back into the Codex build graph. - Use Case: You need to move Codex to a new V8 release. The Skill updates every pinned surface, runs the checksum helper scripts, verifies the canary build, and if it fails, identifies the exact upstream change and the Codex file that must be fixed. ## Quick Start Use the update-v8-version skill to bump Codex to the latest v8 release and validate the release-candidate path.

Frequently Asked Questions about update-v8-version

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update the pinned v8 version in a Rust project?▼

Follow the version-bump sequence in third_party/v8/README.md, then update Cargo.toml, Cargo.lock, MODULE.bazel, BUILD.bazel, and the rusty_v8 sha256 manifest. Run the rusty_v8_bazel.py helper scripts to keep checksums in sync.

How do I validate a rusty_v8 release candidate before publishing?▼

Check the v8-canary CI workflow result for the candidate branch or PR using GitHub check tooling or the gh CLI. If CI is unavailable, run the closest local build validation and clearly note it is a local substitute, not the hosted canary.

Why does a v8 version update fail to build?▼

Failures usually come from upstream deltas: generated binding layout changes, archive or asset naming changes, GN/Bazel target changes, custom libc++ inputs, or patches that no longer apply. Compare the pinned and target versions in denoland/rusty_v8 and upstream V8 to find the breaking delta.

Does this workflow publish releases or tags automatically?▼

No. The workflow stops after the canary path passes and summarizes the result. It does not publish tags, releases, or pushes unless the user explicitly requests it.

What files carry the v8 version pin in Codex?▼

The pin lives in codex-rs/Cargo.toml, codex-rs/Cargo.lock, MODULE.bazel, third_party/v8/BUILD.bazel, third_party/v8/README.md, and the matching third_party/v8/rusty_v8_<version>.sha256 manifest.