fix(tempo): respect token metadata batching config - #4956
Merged
Conversation
🦋 Changeset detectedLatest commit: 5e25f5e The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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 |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
commit: |
struong
enabled auto-merge (squash)
August 4, 2026 17:22
tmm
disabled auto-merge
August 4, 2026 17:34
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Updates Tempo token metadata reads to honor explicit client multicall configuration while preserving deployless Multicall3 as the action's default.
Motivation
Zone clients cannot execute deployless contract-creation
eth_callrequests. Explicitly disabling client multicall should allowtoken.getMetadatato use ordinary contract reads without changing the default behavior for existing Tempo clients.Changes
readContractcalls when the client explicitly configures multicall behavior.Testing
pnpm test src/tempo/actions/token.test.ts --run— 76 passed, 1 existing skip.pnpm check:typespnpm build:typesVITE_TEMPO_ZONES=true pnpm test src/tempo/actions/zone.test.ts --run; the local Zone container exited before tests because the configured dev key did not ownZoneFactory.