Bump resilience4j-retry from 1.6.1 to 1.7.0 #232
Merged
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
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
dependabot
bot
added
the
dependencies
|
@dependabot rebase |
Bumps [resilience4j-retry](https://github.com/resilience4j/resilience4j) from 1.6.1 to 1.7.0. - [Release notes](https://github.com/resilience4j/resilience4j/releases) - [Changelog](https://github.com/resilience4j/resilience4j/blob/master/RELEASENOTES.adoc) - [Commits](resilience4j/resilience4j@v1.6.1...v1.7.0) Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
force-pushed
the
dependabot/maven/io.github.resilience4j-resilience4j-retry-1.7.0
branch
from
b7fff2d to
f489218
Compare
|
Kudos, SonarCloud Quality Gate passed!
|
slawekjaranowski
approved these changes
Jan 30, 2021
slawekjaranowski
deleted the
dependabot/maven/io.github.resilience4j-resilience4j-retry-1.7.0
branch
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.
Bumps resilience4j-retry from 1.6.1 to 1.7.0.
Release notes
Sourced from resilience4j-retry's releases.
Changelog
Sourced from resilience4j-retry's changelog.
Commits
801a291Updated version to 1.7.0e44cbd9Issue #1228: Removed RateLimiter duplications (#1264) (#1303)5730df1Issue #1228: Added RateLimiter drainIfNeeded to RxJava3 (#1264) (#1300)a5087ceIssue #1228: RateLimiter drainPermissionsOnResult refactored to Predicate (#...adf9507Issue #1228: Added RateLimiter drainIfNeeded to Reactor (#1264) (#1299)7fe040eUpdated RELEASENOTESbfe2861Issue #1281: Added failAfterMaxAttempts flag to RetryConfig and a new MaxRetr...4387316Issue #1228: Added onResult and onError hook to RateLimiter and drainPermiss...1a2ed10Retry failing tests up to 3 times (#1286)8ff84c2Updated RELEASNOTESDependabot 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