update-v8-version Skill
Update Codex's pinned v8 / rustyv8 versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds. Use when asked to bump V8, update rustyv8 artifacts, prepare or validate a V8 release candidate, check v8-canary, or diagnose why a V8 version update no longer builds. Published by openai in codex.
Decision snapshot
Is this a fit?
Developers using codex, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
28 days ago · Apache-2.0 license
No specific cautions were detected. Review the source and requested permissions before installing.
What is update-v8-version Skill?
Update Codex's pinned v8 / rustyv8 versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds. Use when asked to bump V8, update rustyv8 artifacts, prepare or validate a V8 release candidate, check v8-canary, or diagnose why a V8 version update no longer builds. Published by openai in codex. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using codex
Declared skill metadata
- Source file: .codex/skills/update-v8-version/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use update-v8-version Skill
- Use it for developers using codex.
Built with
Editorial notes
Source
- Creator: openai
- Repository: openai/codex
- Skill file: .codex/skills/update-v8-version/SKILL.md
What it does
Update Codex's pinned v8 / rustyv8 versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds. Use when asked to bump V8, update rustyv8 artifacts, prepare or validate a V8 release candidate, check v8-canary, or diagnose why a V8 version update no longer builds.
Skill instructions
Update V8 Version Core Workflow 1. Read thirdparty/v8/README.md and follow its version-bump sequence. Treat that document as the release-process source of truth. 2. 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<version.sha256 manifest when the remaining prebuilt inputs change 3. Keep the existing checksum helpers in the loop: bash python3 .github/scripts/rustyv8bazel.py update-module-bazel python3 .github/scripts/rustyv8bazel.py check-module-bazel python3 -m unittest discover -s .github/scripts -p testrustyv8bazel.py 4. 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 tha
Verified compatibility and discovery
Frequently asked questions
What is update-v8-version?
update-v8-version is a open-source AI agent skill with Copy skill directory. Update Codex's pinned v8 / rustyv8 versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds.
Who is update-v8-version best for?
update-v8-version is best for reusing agent instructions, scripts, and references.
How do I install update-v8-version?
Install or run update-v8-version using Copy skill directory. Check update-v8-version for the latest setup command.
Is update-v8-version actively maintained?
update-v8-version may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
