update-v8-version

Update pinned v8 and rusty_v8 versions across MODULE.bazel, Cargo.toml, and third_party/v8.

4|1|Updated Oct 5, 2024
One-click install
npx skills add https://github.com/xrehpicx/anya --skill update-v8-version
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-v8-version
Source: https://github.com/xrehpicx/anya/tree/main/.codex/skills/update-v8-version
Command: npx skills add https://github.com/xrehpicx/anya --skill update-v8-version

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bumps and validates pinned V8 versions across the Codex repository to prevent breakages from upstream changes and to ensure release candidates are properly validated.

Core Features & Use Cases

  • Pin and update Codex's pinned v8 / rusty_v8 versions across repository surfaces.
  • Validate the release-candidate path and investigate failed v8 canary or artifact builds.
  • Coordinate with CI and pre-release checks to maintain a stable build.

Quick Start

Run the update-v8-version workflow to bump v8 pins and verify 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 V8 version in my Bazel and Cargo repository surfaces?

To update V8 versions, pin and apply changes across MODULE.bazel, codex-rs/Cargo.toml, and third_party/v8 to ensure a valid release-candidate path and canary success.

What causes a V8 canary build to fail after an upstream version bump?

A V8 canary build fails when upstream changes introduce breakages in the pinned V8 or rusty_v8 versions, requiring validation of the release-candidate path to investigate and resolve the failures.

How do I validate a V8 release candidate before running CI checks?

You validate a V8 release candidate by applying version pins across repository surfaces, enforcing validation steps, running local checks, and documenting outcomes for both success and failure scenarios.

Do I need to manually update Cargo.toml and MODULE.bazel when bumping rusty_v8?

No, updating rusty_v8 requires applying changes to both codex-rs/Cargo.toml and MODULE.bazel to coordinate with CI and pre-release checks to maintain a stable build.

What is the best way to maintain a stable build when updating V8 dependencies?

The best way to maintain a stable build when updating V8 dependencies is to coordinate with CI and pre-release checks while enforcing validation steps and documenting outcomes for both success and failure.