fix: preserve retro compatibility of claim events indexing (cherry-pick) #1441
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.



🔄 Changes Summary
Make indexing of claim events backward compatible in a way that even for the sovereign chain deployments (namely the one which deploy the
AgglayerBridgeL2), we still index theClaimEventas well. On the first occurrence ofDetailedClaimEvent, we inhibit the further processing of the (legacy)ClaimEvent.This PR brings a couple of minor changes not related to the retro compatibility of claim events indexing:
lastDepositCounton theAgglayerBridgecontract failsgolangci-lint-v2. This change also requiresgolangci-lint-v2to be installed in theGOPATHN/A
📋 Config Updates
N/A
✅ Testing
🐞 Issues
🔗 Related PRs
📝 Notes
Cherry pick of #1435