Bump resilience4j-retry from 1.6.0 to 1.6.1

[dependabot]

Bumps resilience4j-retry from 1.6.0 to 1.6.1.

Changelog

Sourced from resilience4j-retry's changelog.

= Release Notes

== Version 0.1.0

• Initial version

=== Version 0.1.1

• Added the functionality to add exceptions with are ignored by the CircuitBreaker

=== Version 0.1.2

• Added the feature to get Metrics for function executions

=== Version 0.1.3

• Added a static factory method for the CircuitBreakerConfig builder

=== Version 0.1.4

• Added the feature to retry a failed function

=== Version 0.1.5

• Added builders to simplify chaining of decorators

=== Version 0.1.6

• Renamed project to javaslang-circuitbreaker

=== Version 0.1.7

• Fixed Issue #2
• Issue #3 Added a listener mechanism for state transitions

== Version 0.2.0

• Removed Dropwizard Metrics, because its a too heavy dependency for such a lightweight library.
• Changed the way exceptions can be handled. You have to provide a Predicate now instead of a list of exceptions to ignore.

== Version 0.3.0

• The CircuitBreaker is based on a Ring Bit Buffer and a failure rate now.

=== Version 0.3.1

• Changed the visibility of CircuitBreakerUtils.isCallPermitted to public.

=== Version 0.3.2

• CircuitBreakerRegistry has a new method which takes a Supplier of a CircuitBreakerConfig so that the CircuitBreakerConfig is only created when needed.

=== Version 0.3.3

• CircuitBreaker has a new method getCircuitBreakerConfig which allows to retrieve the CircuitBreakerConfig of the CircuitBreaker.
• Renamed the state HALF_CLOSED to HALF_OPEN to match the pattern description of Martin Fowler.

=== Version 0.3.4

• Added a Metrics interface to the CircuitBreaker which allows to retrieve current statistics like failureRate and number of buffer calls.

== Version 0.4.0

• Updated javaslang from 2.0.0-RC4 to 2.0.1

... (truncated)

Commits

• See full diff 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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities (and 0 Security Hotspots to review)
0 Code Smells

No Coverage information
0.0% Duplication