v0.8.3-rc1

🔄 Changes Summary

#1479 - Treat already-monitored GER tx as expected (PR #1503)

• Treats `ErrAlreadyExists` from `ethtxmanager` as expected behavior (not an error) in `submitTransaction`
• Updates `zkevm-ethtx-manager` from v0.2.17 to v0.2.18

#1540 - Adjust REST timeouts (PR #1557)

• Increate timeouts because previous values were too short for slow queries and long-running REST requests (e.g. Bridge claim call)

What's Changed

• feat: cherry-pick PR #1503 and #1557 into release/0.8 by @joanestebanr in #1560

Full Changelog: v0.8.2...v0.8.3-rc1

v0.8.2

NOTE: Is a promotion of v0.8.2-rc4, so it's exactly same code

🔄 Changes Summary

• Add remove GER tool
• Add endpoints on the bridge service to support remove GER tool

🐞 Issues

• aggsender / validator: Fix error calling to eth_getLogs in some RPC providers #1517
• bridgesyncer: Persistent error backfiling some rows in L1 mainnet #1514
• validator: expose metrics for validator #1510
• bridge-service: fix a bug in claims count logic (related to pagination), it affects the end-point /claims #1395
• bridgesyncer: migration files ara equal to 0.9.x and develop, a minor improvement is that migrations from 0.8.0 preserve values of bridge.to_address #1499
• Fix bug for double claim processing

What's Changed

• feat: backport remove-ger tool and supporting bridgesync/bridgeservic… by @arnaubennassar in #1497
• fix: preserve bridge.to_address (partial cherry-pick of PR #1452) v0.8.x by @joanestebanr in #1499
• fix: expose metrics for validator (#1511) by @joanestebanr in #1512
• fix: Error backfilling in case of same tx have multiples bridges by @joanestebanr in #1515
• fix: unset claims max log range (0.8) by @arnaubennassar in #1526

Full Changelog: v0.8.1...v0.8.2

v0.8.2-rc4

🔄 Changes Summary

🐞 Issues

• aggsender / validator: Fix error calling to eth_getLogs in some RPC providers #1517
• bridgesyncer: Persistent error backfiling some rows in L1 mainnet #1514

What's Changed

• fix: Error backfilling in case of same tx have multiples bridges by @joanestebanr in #1515
• fix: unset claims max log range (0.8) by @arnaubennassar in #1526

Full Changelog: v0.8.2-rc3...v0.8.2-rc4

v0.9.0-rc3

🔄 Changes Summary

#1479 - Treat already-monitored GER tx as expected (PR #1503)

• Treats `ErrAlreadyExists` from `ethtxmanager` as expected behavior (not an error) in `submitTransaction`
• Updates `zkevm-ethtx-manager` from v0.2.17 to v0.2.18

#1540 - Adjust REST timeouts (PR #1557)

• Increate timeouts because previous values were too short for slow queries and long-running REST requests (e.g. Bridge claim call)

What's Changed

• feat: cherry-pick PR #1503 and #1557 into release/0.8 by @joanestebanr in #1560

v0.8.2-rc3

🔄 Changes Summary

🐞 Issues

• validator: expose metrics for validator #1510

What's Changed

• fix: expose metrics for validator (#1511) by @joanestebanr in #1512

Full Changelog: v0.8.2-rc2...v0.8.2-rc3

v0.8.2-rc2

🔄 Changes Summary

This release it's to standardize the migration scripts, also fix a minor bug of bridge-service

🐞 Issues

• bridge-service: fix a bug in claims count logic (related to pagination), it affects the end-point /claims #1395
• bridgesyncer: migration files ara equal to 0.9.x and develop, a minor improvement is that migrations from 0.8.0 preserve values of bridge.to_address #1499

What's Changed

• fix: preserve bridge.to_address (partial cherry-pick of PR #1452) v0.8.x by @joanestebanr in #1499

Full Changelog: v0.8.2-rc1...v0.8.2-rc2

v0.8.2-rc1

🔄 Changes Summary

• Fix bug for double claim processing
• Add remove GER tool
• Add endpoints on the bridge service to support remove GER tool

v0.8.1

🔄 Changes Summary

This release introduces support for handling multiple GER (Global Exit Root) injections within the same block by migrating from the imported_global_exit_root table to a new
imported_global_exit_root_v2 table that includes a block_pos column to track the position of each GER within a block. This prevents primary key conflicts when multiple GERs are injected in the same block.

• The legacy downloader set as blockPosition the l1infotreeIndex to avoid duplications

🐞 Issues

• Fixes #1468 - Error when there are 2 or more injected GERs in the same block

Full Changelog: v0.8.0...v0.8.1

• fix: #1468-Error if there are 2 injected GER in the same block (#1469)

v0.9.0-rc2

🔄 Changes Summary

• Fix typo: AggSender.TriggerASAP.DelayBeetweenCertificates
• Fix: If there are 2 injected GER in the same block (#1469) (#1472)

⚠️ Breaking Changes

• Deprecated config field AggSender.TriggerASAP.DelayBeetweenCertificates
  in favour of DelayBetweenCertificates:

📋 Config Updates

```
[AggSender.TriggerASAP]
    DelayBetweenCertificates = "1s"
```

What's Changed

• fix: cherrypick #1468-Error if there are 2 injected GER in the same block (#1469) by @joanestebanr in #1472
• fix: cherry-pick #1471 Fix typo 'DelayBeetweenCertificates' by @joanestebanr in #1473

Full Changelog: v0.9.0-rc1...v0.9.0-rc2

v0.8.1-rc1

🔄 Changes Summary

This release introduces support for handling multiple GER (Global Exit Root) injections within the same block by migrating from the imported_global_exit_root table to a new
imported_global_exit_root_v2 table that includes a block_pos column to track the position of each GER within a block. This prevents primary key conflicts when multiple GERs are injected in the same block.

• The legacy downloader set as blockPosition the l1infotreeIndex to avoid duplications

🐞 Issues

• Fixes #1468 - Error when there are 2 or more injected GERs in the same block

Full Changelog: v0.8.0...v0.8.1-rc1

• fix: #1468-Error if there are 2 injected GER in the same block (#1469)