From 6fd5b2b337e7ebd629a5870956537298f59854aa Mon Sep 17 00:00:00 2001 From: soyboy Date: Fri, 14 Nov 2025 14:06:27 -0800 Subject: [PATCH] updating version --- notices/fusaka-notice.mdx | 8 ++++---- notices/upgrade-17.mdx | 8 ++++---- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/notices/fusaka-notice.mdx b/notices/fusaka-notice.mdx index 58ed9dd7c..a675ab7a2 100644 --- a/notices/fusaka-notice.mdx +++ b/notices/fusaka-notice.mdx @@ -41,8 +41,8 @@ Fusaka contains various breaking changes. See [EIP-7607: Hardfork Meta - Fusaka] Update your node software as soon as possible after release: - * [op-node/v1.16.1](https://github.com/ethereum-optimism/optimism/releases/tag/op-node%2Fv1.16.1) - * [op-geth/v1.101603.4](https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101603.4) + * [op-node/v1.16.2](https://github.com/ethereum-optimism/optimism/releases/tag/op-node%2Fv1.16.2) + * [op-geth/v1.101603.5](https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101603.5) * [op-reth/v1.9.1](https://github.com/paradigmxyz/reth/releases/tag/v1.9.1) ### Ensure your L1 beacon node endpoint can serve all blobs @@ -76,8 +76,8 @@ Update the following components: | --------------- | ----------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `proxyd` | [v4.19.0](https://github.com/ethereum-optimism/infra/releases/tag/proxyd%2Fv4.19.0) or greater | You need to whitelist `eth_blobBaseFee` rpc if using proxyd for L1 load balancing. If you use `dugtrio` ensure this is also updated to the latest release. | | `op-batcher` | [v1.16.2](https://github.com/ethereum-optimism/optimism/releases/tag/op-batcher%2Fv1.16.2) | The `op-batcher` must be restarted at least once after updating `op-node` to the latest release. The batcher loads the rollup config once at startup and this will need to happen to update the activation timestamps for Jovian. We've opened this [issue](https://github.com/ethereum-optimism/optimism/issues/18178) to improve this experience in the future. | -| `op-node` | [v1.16.1](https://github.com/ethereum-optimism/optimism/releases/tag/op-node%2Fv1.16.1) | L1 chain config must be supplied via a new flag (see the release notes). Not necessary for chains deriving from Ethereum Mainnet, Sepolia, Holesky or Hoodi. | -| `op-geth` | [v1.101603.4](https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101603.4) | | +| `op-node` | [v1.16.2](https://github.com/ethereum-optimism/optimism/releases/tag/op-node%2Fv1.16.2) | L1 chain config must be supplied via a new flag (see the release notes). Not necessary for chains deriving from Ethereum Mainnet, Sepolia, Holesky or Hoodi. | +| `op-geth` | [v1.101603.5](https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101603.5) | | | `op-challenger` | [v1.7.0](https://github.com/ethereum-optimism/optimism/releases/tag/op-challenger%2Fv1.7.0) | If deriving from a chain other than Ethereum Mainnet, Sepolia or Hoodi then L1 chain config must be supplied via a new flag. | | `kona-node` | [v1.2.2](https://github.com/op-rs/kona/releases/tag/kona-node%2Fv1.2.2) | | | `kona-host` | [v1.2.2](https://github.com/op-rs/kona/releases/tag/kona-host%2Fv1.2.2) | | diff --git a/notices/upgrade-17.mdx b/notices/upgrade-17.mdx index 3b10dddbc..8f80c43ec 100644 --- a/notices/upgrade-17.mdx +++ b/notices/upgrade-17.mdx @@ -54,8 +54,8 @@ These following steps are necessary for every node operator: The releases contain both the Jovian Mainnet and Sepolia Superchain activation timestamps. - * [op-node/v1.16.1](https://github.com/ethereum-optimism/optimism/releases/tag/op-node%2Fv1.16.1) - * [op-geth/v1.101603.4](https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101603.4) + * [op-node/v1.16.2](https://github.com/ethereum-optimism/optimism/releases/tag/op-node%2Fv1.16.2) + * [op-geth/v1.101603.5](https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101603.5) * [op-reth/v1.9.1](https://github.com/paradigmxyz/reth/releases/tag/v1.9.1) @@ -90,8 +90,8 @@ Update the following components: | --------------- | ----------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `proxyd` | [v4.19.0](https://github.com/ethereum-optimism/infra/releases/tag/proxyd%2Fv4.19.0) or greater | You need to whitelist `eth_blobBaseFee` rpc if using proxyd for L1 load balancing. If you use `dugtrio` ensure this is also updated to the latest release. | | `op-batcher` | [v1.16.2](https://github.com/ethereum-optimism/optimism/releases/tag/op-batcher%2Fv1.16.2) | The `op-batcher` must be restarted at least once after updating `op-node` to the latest release. The batcher loads the rollup config once at startup and this will need to happen to update the activation timestamps for Jovian. We've opened this [issue](https://github.com/ethereum-optimism/optimism/issues/18178) to improve this experience in the future. | -| `op-node` | [v1.16.1](https://github.com/ethereum-optimism/optimism/releases/tag/op-node%2Fv1.16.1) | L1 chain config must be supplied via a new flag (see the release notes). Not necessary for chains deriving from Ethereum Mainnet, Sepolia, Holesky or Hoodi. | -| `op-geth` | [v1.101603.4](https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101603.4) | | +| `op-node` | [v1.16.2](https://github.com/ethereum-optimism/optimism/releases/tag/op-node%2Fv1.16.2) | L1 chain config must be supplied via a new flag (see the release notes). Not necessary for chains deriving from Ethereum Mainnet, Sepolia, Holesky or Hoodi. | +| `op-geth` | [v1.101603.5](https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101603.5) | | | `op-challenger` | [v1.7.0](https://github.com/ethereum-optimism/optimism/releases/tag/op-challenger%2Fv1.7.0) | If deriving from a chain other than Ethereum Mainnet, Sepolia or Hoodi then L1 chain config must be supplied via a new flag. | | `kona-node` | [v1.2.2](https://github.com/op-rs/kona/releases/tag/kona-node%2Fv1.2.2) | | | `kona-host` | [v1.2.2](https://github.com/op-rs/kona/releases/tag/kona-host%2Fv1.2.2) | |