> ## Documentation Index
> Fetch the complete documentation index at: https://docs.optimism.io/llms.txt
> Use this file to discover all available pages before exploring further.

# op-conductor Releases

> Release history for op-conductor. High-availability sequencer coordination service.

**op-conductor** manages sequencer high-availability using Raft consensus, coordinating a multi-node sequencer cluster to ensure no unsafe reorgs and continuous uptime with up to one node failure.

<Update label="May 18, 2026" description="v0.9.4" tags={["Latest", "Stable"]}>
  This release includes bug fixes for cluster stability and leader failover, a new round-robin leadership transfer feature, and
  removal of the deprecated op-supervisor health check integration. It also ensures that the version label is filled with build info from CI.

  What's Changed in op-conductor/v0.9.4

  * [CI build bug ](https://github.com/ethereum-optimism/optimism/pull/19809)has been fixed to ensure `version` label is filled
  * fix(op-conductor): disable raft ShutdownOnRemove to prevent zombie nodes by @KyrinCode in
    [https://github.com/ethereum-optimism/optimism/pull/18699](https://github.com/ethereum-optimism/optimism/pull/18699)
  * feat(conductor): fix leader loop switch by adding round-robin leadership transfer by @KyrinCode in
    [https://github.com/ethereum-optimism/optimism/pull/18697](https://github.com/ethereum-optimism/optimism/pull/18697)
  * chore: replace deprecated deps with stdlib equivalents by @sebastianst in [https://github.com/ethereum-optimism/optimism/pull/20014](https://github.com/ethereum-optimism/optimism/pull/20014)
  * op-node: remove deprecated ProtocolVersions watching by @sebastianst in [https://github.com/ethereum-optimism/optimism/pull/20311](https://github.com/ethereum-optimism/optimism/pull/20311)
  * chore(op-conductor): remove op-supervisor support by @ajsutton in [https://github.com/ethereum-optimism/optimism/pull/20781](https://github.com/ethereum-optimism/optimism/pull/20781)

  Full Changelog: [https://github.com/ethereum-optimism/optimism/compare/op-conductor/v0.9.3...op-conductor/v0.9.4](https://github.com/ethereum-optimism/optimism/compare/op-conductor/v0.9.3...op-conductor/v0.9.4)

  🚢 Docker Image: [https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-conductor:v0.9.4](https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-conductor:v0.9.4)

  [View full release on GitHub →](https://github.com/ethereum-optimism/optimism/releases/tag/op-conductor/v0.9.4)
</Update>

<Update label="March 31, 2026" description="v0.9.3" tags={["Stable"]}>
  This release is optional; however, we recommend updating as it includes a Go version upgrade addressing security fixes, along with enhanced container image hardening.

  [View full release on GitHub →](https://github.com/ethereum-optimism/optimism/releases/tag/op-conductor/v0.9.3)
</Update>

<Update label="October 30, 2025" description="v0.9.0" tags={["Stable"]}>
  This release supports deserialisation of rollup configs, passed at the command line, which contain fields introduced with the Jovian hardfork (which can appear in the rollup config even before Jovian is active).

  [View full release on GitHub →](https://github.com/ethereum-optimism/optimism/releases/tag/op-conductor/v0.9.0)
</Update>

<Update label="October 6, 2025" description="v0.8.0" tags={["Stable"]}>
  ## What's Changed

  * feat(op-conductor): rollup-boost partial unhealthiness tolerance by @yashvardhan-kukreja in [https://github.com/ethereum-optimism/optimism/pull/17633](https://github.com/ethereum-optimism/optimism/pull/17633)

  [View full release on GitHub →](https://github.com/ethereum-optimism/optimism/releases/tag/op-conductor/v0.8.0)
</Update>

<Update label="September 10, 2025" description="v0.7.3" tags={["Stable"]}>
  ## What's Changed

  * op-conductor: p2p healthcheck fix and execution\_p2p\_healthcheck\_api\_type by @yashvardhan-kukreja in [https://github.com/ethereum-optimism/optimism/pull/17294](https://github.com/ethereum-optimism/optimism/pull/17294)

  **Full Changelog**: [https://github.com/ethereum-optimism/optimism/compare/op-conductor/v0.7.2...op-conductor/v0.7.3](https://github.com/ethereum-optimism/optimism/compare/op-conductor/v0.7.2...op-conductor/v0.7.3)

  [View full release on GitHub →](https://github.com/ethereum-optimism/optimism/releases/tag/op-conductor/v0.7.3)
</Update>

<Update label="June 10, 2025" description="v0.7.0" tags={["Stable"]}>
  ## What's Changed

  * add conductor support for flashblocks websocket by @angel-ding-cb in [https://github.com/ethereum-optimism/optimism/pull/15681](https://github.com/ethereum-optimism/optimism/pull/15681)

  [View full release on GitHub →](https://github.com/ethereum-optimism/optimism/releases/tag/op-conductor/v0.7.0)
</Update>

<Update label="May 12, 2025" description="v0.5.1-rc.3" tags={["Release Candidate"]}>
  ## Transparent and unconditional proxy for throttling messages

  In this release the conductor is updated to forward `miner_setMaxDASize` API calls

  * transparently -- that is, returning an error if the origin sequencer returns an error, and
  * unconditionally -- that is, proxying the call even if the origin sequencers is not currently the leader

  > \[!IMPORTANT]
  > It is strongly recommended to upgrade. If updating to the latest op-batcher release, it is required to upgrade to this version of op-conductor too, because starting with this batcher release, all endpoints are always throttled, not only the active sequencer.

  [View full release on GitHub →](https://github.com/ethereum-optimism/optimism/releases/tag/op-conductor/v0.5.1-rc.3)
</Update>
