Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(op-stack): add support for new LegacyGame error #3360

Merged
merged 2 commits into from
Feb 18, 2025

Conversation

smartcontracts
Copy link
Contributor

Adds support for the new LegacyGame error that contracts would start to return if an upcoming proposal is accepted. Note that this change is fully backwards compatible.

Also cleans up this section of the code so it's easier to add or remove errors as needed.

Copy link

vercel bot commented Feb 18, 2025

@smartcontracts is attempting to deploy a commit to the Wevm Team on Vercel.

A member of the Team first needs to authorize it.

Copy link

changeset-bot bot commented Feb 18, 2025

🦋 Changeset detected

Latest commit: 3e67616

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
viem Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Adds support for the new LegacyGame error that contracts would
start to return if an upcoming proposal is accepted. Note that
this change is fully backwards compatible.

Also cleans up this section of the code so it's easier to add or
remove errors as needed.
@smartcontracts smartcontracts force-pushed the sc/legacy-game-and-cleanup branch from 212976d to acce99f Compare February 18, 2025 20:50
@jxom jxom merged commit efa2252 into wevm:main Feb 18, 2025
2 of 3 checks passed
@github-actions github-actions bot mentioned this pull request Feb 18, 2025
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.

2 participants