Skip to content

op-deployer: harden and ship the forge path; make it the default for live deploys #23302

Closed

Description

@sebastianst

Make forge the default for the live target and bootstrap, and make forge a dependable runtime dependency.

Correctness

  • SetDisputeGameImpl always runs on the Go host (dispute_games.go#L163, #L246), whose fork is pinned at start and can't see contracts forge deployed earlier in the same apply. Add a runWithBytes entrypoint and a forge caller.
  • Don't construct the Go host or opcm.NewScripts in forge mode.
  • Preflight that the bundle has foundry.toml and the runWithBytes selectors, with a clear error on mismatch.
  • Never recompile at runtime: run --offline, fail if forge reports a compile, propagate FOUNDRY_PROFILE. Prewarm the script graph in every bundle producer (Docker, melange, CI, publish).
  • Use a per-invocation FOUNDRY_BROADCAST directory so concurrent runs don't collide ([Forge Deployer] Fix op-e2e tests with parallel op-deployer #18760).

Distribution

  • Docker and apko images already ship a pinned forge; keep them without solc.
  • Keep the auto-download for Linux and macOS. Drop the Windows release targets (Windows auto-download is broken today).
  • Respect --cache-dir for the forge binary, give a clear error when offline, and autodetect musl instead of requiring FORGE_ENV=alpine.
  • Document forge as a runtime dependency, including for Go library users (sysgo/devstack consumers).

Tests, then flip

🤖 Co-created with Claude Opus 5.5

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions