Repository navigation
fix: require hardhat-zod-utils 3.0.9 in hardhat and hardhat-ledger - #8843
Merged
schaable merged 2 commits intoNov 13, 2026
Merged
Conversation
🦋 Changeset detectedLatest commit: 05ef08c The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
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 |
hardhat-zod-utils 3.0.9 requires hardhat-utils 5.1.1 (NomicFoundation#8791), whose hexStringToBytes no longer decodes "0x" as a zero byte (NomicFoundation#8765). Both packages still accepted 3.0.5, so a lockfile holding 3.0.8 kept the old parsing through a hardhat upgrade. Part of NomicFoundation#8790. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
schaable
force-pushed
the
fix/hardhat-ledger-zod-utils-floor
branch
from
November 13, 2026 17:08
7f90256 to
05ef08c
Compare
schaable
approved these changes
Nov 13, 2026
schaable
left a comment
Member
There was a problem hiding this comment.
Thanks for following up on this!
I pushed a few changes to your branch:
- Rebased it on the latest
main. - Bumped
hardhat's@nomicfoundation/hardhat-utilsrange to^5.1.1. Your change already covers local accounts throughhardhat-zod-utils, buthardhatalso callshexStringToBytesdirectly, so it needs to require the fixed version too. - Shortened the
hardhatchangeset to one line.
Looks good to me now.
schaable
enabled auto-merge
November 13, 2026 17:14
Merged
via the queue into
NomicFoundation:main
with commit Nov 13, 2026
0e96c9f
246 of 247 checks passed
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
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.
Closes #8790
The follow-up to #8791, now that
@nomicfoundation/hardhat-zod-utils3.0.9 is out.3.0.9 requires
@nomicfoundation/hardhat-utils5.1.1 (#8791), whosehexStringToBytesno longer decodes"0x"as a zero byte (#8765).hardhatandhardhat-ledgerstill acceptedhardhat-zod-utils^3.0.5, so a lockfile holding 3.0.8 kept the oldrpcDataparsing through ahardhatupgrade. Local accounts then signeddata: "0x"as calldata0x00, andpersonal_sign/eth_signof"0x"as the message0x00(repro in #8790).Changes
packages/hardhatandpackages/hardhat-ledger:@nomicfoundation/hardhat-zod-utilsworkspace:^3.0.5→workspace:^3.0.9.pnpm-lock.yaml: the two specifiers.hardhatand@nomicfoundation/hardhat-ledger.In the signing paths, request data reaches
hexStringToBytesonly throughhardhat-zod-utils; the direct call inlocal-accounts.tsparses private keys. So this PR leaves thehardhat-utilsranges of both packages as they are.Tests
No new tests: this only changes version ranges, and the parsing is covered by the tests added in #8791.
scripts/check-dependencies.tspasses; the local-accounts tests (62) and thehardhat-ledgertests (56) pass.🤖 Generated with Claude Code