[ci] release - #346
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
June 24, 2026 18:05
44a56c8 to
6144837
Compare
|
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.
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
@ensdomains/ensjs@4.3.1
Patch Changes
477befdThanks @v1rtl! -getNamenow enforces normalization: it only returns a primary name if the value returned by reverse resolution is already in its normalised form, returningnullotherwise (instead of silently coercing it). This mirrors viem'sgetEnsNamebehaviour (Fix: ENSgetEnsName()should enforce normalization wevm/viem#4756) and brings v4 in line with v5 (WEB-533). The normalization check is applied to both the matching andallowMismatchpaths.@ensdomains/ensjs-react@0.0.9
Patch Changes
477befd]: