Skip to content

Move V8 patch management into rusty_v8#1944

Open
bartlomieju wants to merge 1 commit intomainfrom
consolidate-v8-patch-management
Open

Move V8 patch management into rusty_v8#1944
bartlomieju wants to merge 1 commit intomainfrom
consolidate-v8-patch-management

Conversation

@bartlomieju
Copy link
Copy Markdown
Member

Summary

  • Move V8 patch files from denoland/v8 repo into patches/ directory in this repo
  • Rewrite tools/auto_update_v8.ts to be a single unified script that fetches upstream V8 directly, applies patches, pushes to the denoland/v8 fork, and updates all deps
  • Remove dependency on denoland/v8's separate autoroll cron job

Previously managing V8 patches required coordinating two repos (denoland/v8 and denoland/rusty_v8) with two separate cron jobs. Cherry-picking a commit or adding a patch meant working in denoland/v8 first, waiting for its autoroll to run, then waiting for rusty_v8's autoroll to pick it up.

Now:

  • Add a patch: drop a .patch file in patches/
  • Bump V8 version: change V8_VERSION at the top of auto_update_v8.ts
  • Cherry-pick a commit: generate a patch file and add it to patches/

The denoland/v8 repo remains as a submodule host but its autoroll workflow can be disabled.

Test plan

  • Verify deno run -A ./tools/auto_update_v8.ts works end-to-end
  • Disable autoroll workflow in denoland/v8 after merging

🤖 Generated with Claude Code

Previously V8 patches were managed in a separate denoland/v8 repo with
its own autoroll script and CI job. This required coordinating two repos
and two cron jobs just to apply patches on top of upstream V8.

Now everything lives in rusty_v8:
- patches/ directory contains the V8 patch files
- tools/auto_update_v8.ts fetches upstream V8 directly, applies patches,
  pushes to the denoland/v8 fork, and updates rusty_v8 deps — all in one
  step
- Single cron job instead of two

To add a new patch: drop a .patch file in patches/
To bump V8 version: change V8_VERSION at the top of auto_update_v8.ts

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant