Bump failsafe from 2.4.3 to 2.4.4
Bumps failsafe from 2.4.3 to 2.4.4.
Changelog
Sourced from failsafe's changelog.
2.4.4
Bug Fixes
- Fixed #298 -
Fallback.onFailedAttemptnot being called correctlyImprovements
- Fixed #296 - Add Automatic-Module-Name entry to the generated manifest file
API Changes
- Added a generic result type
RtoExecutionContext,Execution,AsyncExecution, andAsyncRunnable. This ensures that result types are unified across the API. It does mean that there are a few minor breaking changes to the API:
ContextualSuppliernow has an additional result type parameterR. Normally this type is used as lambda parameters where the type is inferred, so most users should not be impacted. But any explicit generic declaration of this type will not compile until the new parameter is added.PolicyExecutor, which is part of the SPI, now accepts an additional result type parameterR. This is only relevant for SPI users who are implementing their own Policies.- Changed
FailsafeExecutor.getAsyncExecutionto acceptAsyncRunnableinstead ofAsyncSupplier. This is a breaking change for anygetAsyncExecutioncalls, but the fix is to simply remove anyreturnstatement. The reason for this change is that the provided object does not need to return a result since the result will already be passed asynchronously to one of theAsyncExecutioncompleteorretrymethods.
Commits
e992fce[maven-release-plugin] prepare release failsafe-2.4.415d539cFix Fallback.onFailedAttemptd057983Added Automatic-Module-Name entry to the generated manifest file (#296)34a38f6Improve javadocs wrt FailurePolicy exception handling conditionsad163c1Create maven.yml2e37486Be slightly more defensive when clearing the forkJoinPoolThread ref in Delega...19dfd28Update push-javadoc for the separate website repo062b910Update links for failsafe.dev domainc446faeChanged FailsafeExecutor.getAsyncExecution to accept an AsyncRunnable9ae6438Added result type params and unified result types- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
@dependabot rebase
Will be fixed with #1394
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.
If you change your mind, just re-open this PR and I'll resolve any conflicts on it.