Skip to content

Conversation

@StanislavBreadless
Copy link
Contributor

What ❔

Why ❔

Checklist

  • PR title corresponds to the body of PR (we generate changelog entries from PRs).
  • Tests for the changes have been added / updated.
  • Documentation comments have been added / updated.
  • Code has been formatted via zkstack dev fmt and zkstack dev lint.

dimazhornyk
dimazhornyk previously approved these changes Jan 20, 2025
@StanislavBreadless StanislavBreadless changed the title erc20 workaround for gateway upgrade fix(gateway): erc20 workaround for gateway upgrade Jan 20, 2025
@StanislavBreadless StanislavBreadless added this pull request to the merge queue Jan 21, 2025
Merged via the queue into main with commit c140ba8 Jan 21, 2025
33 checks passed
@StanislavBreadless StanislavBreadless deleted the sb-erc20-upgrade-workaround branch January 21, 2025 07:48
github-merge-queue bot pushed a commit that referenced this pull request Jan 21, 2025
🤖 I have created a release *beep* *boop*
---


##
[26.1.0](core-v26.0.0...core-v26.1.0)
(2025-01-21)


### Features

* update l2 erc20 bridge address in updater as well
([#3500](#3500))
([fe3c7b2](fe3c7b2))
* **vm:** Implement call tracing for fast VM
([#2905](#2905))
([731b824](731b824))


### Bug Fixes

* copy special case to fast VM call tracer
([#3509](#3509))
([995e583](995e583))
* fix execute encoding for transactions
([#3501](#3501))
([4c381a8](4c381a8))
* **gateway:** erc20 workaround for gateway upgrade
([#3511](#3511))
([c140ba8](c140ba8))


### Performance Improvements

* optimize get_unsealed_l1_batch_inner
([#3491](#3491))
([9b121c9](9b121c9))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

---------

Co-authored-by: zksync-era-bot <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants