Skip to content

chore(main): release taiko-alethia-protocol 3.2.0 - #21889

Open
taiko-kitty wants to merge 1 commit into
mainfrom
release-please--branches--main--components--taiko-alethia-protocol
Open

taiko-kitty wants to merge 1 commit into
mainfrom
release-please--branches--main--components--taiko-alethia-protocol

Conversation

@taiko-kitty

@taiko-kitty taiko-kitty commented Jul 2, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

3.2.0 (2026-10-09)

Features

  • protocol,taiko-client: raise inbox basefee sharing to 100% and rotate raiko2 to v0.9.0 (Proposal0026) (#22127) (6d1d627)
  • protocol: add optional SGX quote-freshness gate (bound quote age) (#21895) (bc3fcf1)
  • protocol: add Proposal0020 to revamp the security council (#22010) (133f290)
  • protocol: add raiko2 v0.8.0-rc1 verifier rotation proposal (#22033) (5738ba1)
  • protocol: create Proposal0025 to disable bridge recalls and move the NFT vaults onto the shared resolvers (#22157) (87e75ec)
  • protocol: disable message recalls and failure marking in the bridge (#22156) (3ef2366)
  • protocol: enable Osaka in genesis test runtime (#22061) (ba45e83)
  • protocol: enable Unzen hardfork — re-enable forced inclusions, mandate ZK proofs (#21924) (eb11224)
  • protocol: Proposal0019 — Unzen hardfork DAO bundle (#21935) (ed7604b)
  • protocol: Proposal0023 upgrades the L1 and L2 bridges and ERC20 vaults (#22083) (15810fd)
  • protocol: support EIP-2612 permit and Permit2 in ERC20Vault (#22093) (fda424d)

Bug Fixes

  • protocol: budget the bridge's Ether sends for EIP-8037 state-creation repricing (#22077) (028be67)
  • protocol: deploy SP1 v6.1 verifier (#21907) (8a330c7)
  • protocol: make SGX MRENCLAVE/MRSIGNER untrust permanent (no silent revival) (#21894) (fa5fb6f)
  • protocol: reject SGX instance ids that overflow the uint32 proof field (#21892) (ac7a154)
  • protocol: restore ACTIVATE_INBOX in L1 deploy script for CI (edf1a42)

Chores

  • protocol: backfill changelog and versions for v3.0.0/v3.1.0 releases (#21886) (c947d9d)
  • protocol: fix comment typos flagged by CI (32e9db6)
  • protocol: merge taiko-alethia-protocol-v3.0.0 (v3.1.0 + hardening) back to main (f837160)
  • protocol: merge taiko-alethia-protocol-v3.0.0 back to main (realign main with prod) (#21922) (bcba1ff)
  • protocol: record the v3.0.0 merge ancestry (take 2) (9646f55)
  • protocol: record the v3.0.0 merge ancestry (take 2) (bc35381)
  • protocol: record the v3.0.0 merge ancestry lost by squashing #21922 (#21930) (ca16fba)
  • protocol: set all foundry profiles to the osaka EVM (#22022) (1617157)

Documentation

  • protocol: correct and document the bridge's gas-schedule assumptions (#22059) (1f19fdf)
  • protocol: create kimi-k3-audit.md (#21978) (6130ec1)
  • protocol: cross-repo Taiko Shasta data-verification audit report (#21979) (c825611)
  • protocol: fix sequencer address NatSpec (#22050) (a1b36f9)
  • protocol: reconcile mainnet + Hoodi contract logs to live on-chain state (#21927) (aa5c1bf)
  • protocol: record Proposal0021 (raiko2 v0.8.0-rc1) in mainnet L1 contract logs (#22148) (5e443b3)
  • protocol: record the Hoodi bridge and ERC20 vault upgrade of Proposal0023 (#22118) (62bd5ee)
  • protocol: record the Hoodi inbox upgrade to basefeeSharingPctg 100 (#22149) (e6a96f8)
  • protocol: record Unzen (Proposal0019) changes in mainnet L1 contract logs (#21991) (d2ee60f)
  • protocol: remove stale self-referential comment from ERC20Vault (#22131) (95a1061)
  • protocol: update mainnet contract logs for Proposal0024 (#22120) (a9f7628)
  • protocol: upgrade inbox to support secure sgx verifier (#21939) (fc762c2)

Code Refactoring

  • protocol: move permissionless preconf to its own branch (#21887) (67625be)
  • protocol: renumber Proposal0023 to match the DAO proposal ID (#22155) (126cf5c)
  • protocol: unify L1 and L2 on the transient-storage reentrancy guard (#22058) (f57ccd9)

Tests

  • protocol: tighten the EIP-8037 send-cap tests and correct its comments (#22082) (cd84799)

This PR was generated with Release Please. See documentation.

@taiko-kitty taiko-kitty changed the title chore(main): release taiko-alethia-protocol 2.4.0 chore(main): release taiko-alethia-protocol 3.2.0 Jul 2, 2026
@taiko-kitty
taiko-kitty force-pushed the release-please--branches--main--components--taiko-alethia-protocol branch 12 times, most recently from fece3fe to 1b10c02 Compare July 9, 2026 01:32
@taiko-kitty
taiko-kitty force-pushed the release-please--branches--main--components--taiko-alethia-protocol branch 6 times, most recently from e623596 to a9f0c54 Compare July 15, 2026 02:48
@taiko-kitty
taiko-kitty force-pushed the release-please--branches--main--components--taiko-alethia-protocol branch 6 times, most recently from 81e9acd to 861aadc Compare July 27, 2026 02:11
@taiko-kitty
taiko-kitty force-pushed the release-please--branches--main--components--taiko-alethia-protocol branch 2 times, most recently from 10c9b09 to 0e44400 Compare August 6, 2026 02:34
@taiko-kitty
taiko-kitty requested a review from smtmfft as a code owner August 24, 2026 07:28
@taiko-kitty
taiko-kitty force-pushed the release-please--branches--main--components--taiko-alethia-protocol branch 8 times, most recently from acffcbc to 7a627f6 Compare August 31, 2026 09:27
@taiko-kitty
taiko-kitty force-pushed the release-please--branches--main--components--taiko-alethia-protocol branch 6 times, most recently from 7254bd4 to 4eaeede Compare September 4, 2026 02:45
@taiko-kitty
taiko-kitty force-pushed the release-please--branches--main--components--taiko-alethia-protocol branch 4 times, most recently from 334e492 to 0815874 Compare September 19, 2026 05:32
@taiko-kitty
taiko-kitty force-pushed the release-please--branches--main--components--taiko-alethia-protocol branch 7 times, most recently from b2a08b7 to b9bacf0 Compare September 25, 2026 00:54
@taiko-kitty
taiko-kitty force-pushed the release-please--branches--main--components--taiko-alethia-protocol branch 3 times, most recently from d1f8d61 to 5e2c405 Compare September 30, 2026 03:47

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant