Repository navigation
chore: version packages - #708
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 20, 2026 23:26
c2ac300 to
47000c2
Compare
This branch had an error being deployed
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
ox@1.8.19
Patch Changes
#693
d7b57e1Thanks @gomesalexandre! - FixedAuthorization.toRpc(and soTransactionRequest.toRpc,Transaction.toRpcand theeip7702AuthofUserOperation.toRpc) to encoderandsasuint256quantities without leading zeros, which geth-based nodes require.#690
3f1730cThanks @gomesalexandre! - FixedBinaryStateTree.merkelizehashing a 32-byte zero value as an empty leaf, which did not match EIP-7864.#704
9c3280bThanks @jxom! - FixedBlockOverrides.toRpcand the zodBlockOverridesschemas to encodeprevRandaoas a 32-byte hash.#703
b31cd5dThanks @jxom! - AddedrequestsHash(EIP-7685) toBlock.Block,Block.toRpcand theBlockzod schemas, so post-Prague blocks no longer lose it on a round trip.#712
a1641a2Thanks @HereForTheTechNFT! - FixedSiwe.validateMessageto assume thehttpsscheme when the message omitsscheme, per EIP-4361.#705
061ebb0Thanks @jxom! - FixedSiwe.createMessageandSiwe.parseMessageto accept an IP literaldomainwith an optional port, such as[::1]:3000.#695
ccbb1afThanks @gomesalexandre! - FixedSiwe.isUrito validate the authority of URIs that have a path, soSiwe.createMessagerejects aurior resource such asuri://[::300.0.0.0]/pthe same way it already rejecteduri://[::300.0.0.0].#705
061ebb0Thanks @jxom! - FixedSiwe.createMessageandSiwe.parseMessageaccepting a comma inscheme.#705
061ebb0Thanks @jxom! - FixedSiwe.createMessageto throwInvalidMessageFieldErrorwhenstatementcontains a carriage return,U+2028orU+2029.#691
6b94083Thanks @gomesalexandre! - FixedTransaction.toRpcto encode a legacy transaction'svwithout the one-byte limit, so EIP-155 transactions whosevis above 255 (chain IDs from 110) no longer throwHex.IntegerOutOfRangeError.#694
f0aaee7Thanks @gomesalexandre! - Fixed theox/zodAuthorization.Signedschemas (and soTransaction.Eip7702) to accept RPCrandsvalues below2**248, which nodes send without leading zeros, decoding them to 32-byte hex likeAuthorization.fromRpcand encoding them back to quantities.#701
4c70533Thanks @Iamsohungrynow! - Fixed the zodSignature.Legacyschema to accept EIP-155vvalues above 255.