Mitch/update rc to master #62
Closed
Conversation
This file contains 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
## [4.0.1](v4.0.0...4.0.1) (2023-06-06) ### Bug Fixes * semantic release ([f5a986f](f5a986f))
## [5.0.0](v4.0.0...5.0.0) (2023-06-07) ### ⚠ BREAKING CHANGES * upgrade to core:3.0.0 ### Bug Fixes * semantic release ([f5a986f](f5a986f)) ### Build System * upgrade to core:3.0.0 ([79dbbf5](79dbbf5))
This removes the extra throw of ConnectException on an unknown exception. By allowing Exception to be thrown in the interface, we can allow any non-R4J exception to be handled up the stack.
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.
Summary of Changes
Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Public API Additions/Changes
Please include a description of any new or modified publicly available classes and/or methods (if applicable).
Downstream Consumer Impact
Please include a description of how downstream consumers will be affected (breaking changes, bug fixes, internal behavior modification, etc.). If this PR introduces breaking changes please list out each of the breaking changes, as well as steps for migrating incompatible code.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist: