Take viem 2.56.8 and bump to 0.5.8 - #117
Merged
Merged
Conversation
viem 2.56.8 changes type declarations only: its runtime files differ from 2.56.7 in the version string and one comment, so the coupled settle set moves without a wire-contract change. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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
Part of the 2026-09-21 dependency sweep. viem moves from 2.56.7 to 2.56.8 in the dependency and the override, and the package version moves to 0.5.8 so the release carries it.
viem belongs to the coupled Tempo/MPP settle set, so the release was scoped by byte-diffing both tarballs. The only runtime-file changes are the version string and one added comment in
utils/formatters/formatter. Everything else is type declarations: the upstream fix preserves named formatter return types for exported Tempo chains. With no runtime change on the call path, the move needs no live settle. node-commerce and the four storefronts take the same pin in this sweep.Also merged today on main: the dependabot minor-patch group (
@types/node,knip,tsx) and dotenv 18, which is dev-only, used as vitest'sdotenv/configsetup file.Worked with: Varun. Not done: no other exact pin has moved (mppx 0.10.1, incur 0.5.1, @x402/* 2.26.0, @solana/mpp 0.7.0 are all latest). eslint 10 and TypeScript 7 stay held per the registry; typescript-eslint 8.70.0 still peers
<6.1.0.Type of change
Public API
Unchanged.
Test plan
Locally:
bun run lint,typecheck,knip,test(577 passed, 2 skipped) andbuildall exit 0. The lock resolves a singleviem@2.56.8. OSV overbun.lockfinds no issues. After merge: tagv0.5.8, watch the publish, confirm npm and the Homebrew formula serve it, then moveFLEET_PAY_VERSION.Checklist