Skip to content

fix: use named error when parsing multiaddrs#395

Merged
achingbrain merged 1 commit intomainfrom
chore/use-named-error
Feb 5, 2025
Merged

fix: use named error when parsing multiaddrs#395
achingbrain merged 1 commit intomainfrom
chore/use-named-error

Conversation

@achingbrain
Copy link
Copy Markdown
Member

@achingbrain achingbrain commented Feb 5, 2025

Throw a ParseError instead of an Error

Throw a `ParseError` instead of and `Error`
@achingbrain achingbrain merged commit 5a9d33c into main Feb 5, 2025
19 checks passed
@achingbrain achingbrain deleted the chore/use-named-error branch February 5, 2025 10:33
github-actions bot pushed a commit that referenced this pull request Feb 5, 2025
## [12.3.5](v12.3.4...v12.3.5) (2025-02-05)

### Bug Fixes

* constrain options transport to tcp or udp ([#396](#396)) ([8d5b325](8d5b325))
* use named error when parsing multiaddrs ([#395](#395)) ([5a9d33c](5a9d33c))

### Dependencies

* **dev:** bump sinon from 18.0.1 to 19.0.2 ([#387](#387)) ([e1747b7](e1747b7))
@github-actions
Copy link
Copy Markdown

github-actions bot commented Feb 5, 2025

🎉 This PR is included in version 12.3.5 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant