TheRandomLabs / CurseAPI

A Java library for handling interactions with CurseForge.
MIT License
30 stars 3 forks source link

Bump resilience4jVersion from 1.5.0 to 1.6.0 #37

Closed dependabot-preview[bot] closed 3 years ago

dependabot-preview[bot] commented 3 years ago

Bumps resilience4jVersion from 1.5.0 to 1.6.0. Updates resilience4j-circuitbreaker from 1.5.0 to 1.6.0

Release notes

Sourced from resilience4j-circuitbreaker's releases.

Release v1.6.0

Enhancements

  • RetryConfig.DEFAULT_MAX_ATTEMPTS should be public #1180
  • Circuitbreaker doesn't open when nested TimeLimiter throws TimeOutCancellationException #1123
  • Enhance Server Side Events /circuitbreaker/events #1076
  • CallNotPermittedException should contain circuit breaker name (and possibly other information) #1062
  • Retry: Exponential backoff with constant behaviour after certain time #1044
  • Respecting the clock set in the CircuitBreakerStateMachine for detecting slow calls #734

Bugs

  • Circuit breaker stuck in HALF_OPEN state #935
  • Circuit breaker global fallback seems to not work when annotated method has more than 1 parameter #1174
  • Timelimiter metrics not calculated when using resilince4j-kotlin #1168
  • Problem with registering metrics for more than one circuit breaker #1131
  • ConcurrentModificationException warning log while consuming events #1115
  • CircuitBreakerConfig.Builder.waitDurationInOpenState() false documentation of when the function throws exception #1092
Changelog

Sourced from resilience4j-circuitbreaker's changelog.

== Version 1.5.0

  • Issue #855: Updated resilience4j-spring-boot2 to 2.3.0.RELEASE
  • Issue #855: Updated resilience4j-spring-cloud2 to 2.2.2.RELEASE
  • Issue #942: Introduced new CB metric "notPermittedCalls"
  • Issue #964: Added Kotlin DSL for building *Config and *Registry classes
  • Issue #979: Added fairCallHandlingEnabled flag to BulkheadConfig which controls whether FairSync or NonfairSync should be used in the Semaphore.
  • Issue #982: Added support to configure exponential random backoff via Spring config
  • Issue #991: Fixed bug that auto transition to half_open happens even if the state is forced open.
  • Issue #1000: Added toString to CircuitBreakerConfig
  • Issue #1003: Fixed bug that CircuitBreaker tries to obtain permission twice in circuitBreaker.decorateEitherSupplier()

== Version 1.6.0

=== Enhancements

  • RetryConfig.DEFAULT_MAX_ATTEMPTS should be public #1180
  • Circuitbreaker doesn't open when nested TimeLimiter throws TimeOutCancellationException #1123
  • Enhance Server Side Events /circuitbreaker/events #1076
  • CallNotPermittedException should contain circuit breaker name (and possibly other information) #1062
  • Retry: Exponential backoff with constant behaviour after certain time #1044
  • Respecting the clock set in the CircuitBreakerStateMachine for detecting slow calls #734

=== Bugs

  • Circuit breaker stuck in HALF_OPEN state #935
  • Circuit breaker global fallback seems to not work when annotated method has more than 1 parameter #1174
  • Timelimiter metrics not calculated when using resilince4j-kotlin #1168
  • Problem with registering metrics for more than one circuit breaker #1131
  • ConcurrentModificationException warning log while consuming events #1115
  • CircuitBreakerConfig.Builder.waitDurationInOpenState() false documentation of when the function throws exception #1092
Commits
  • a0f029b Added 1.6.0 RELEASENOTES.adoc
  • 5a77b1d Issue #1044: Added maxWaitDurationInOpenState to limit CircuitBreaker exponen...
  • 49219fc Issue #1044: Added maxInterval to limit exponential backoff - spring properti...
  • 21f6cf8 Issue #1168: Map TimeoutCancellationException to TimeoutException and registe...
  • bec8535 Issue #1180: Made RetryConfig default maxAttempts public (#1184)
  • b5e5079 Issue #1171: Made configs serializable
  • 1846244 Issue #1174: Fixed issue where generic fallback methods wouldn't work for met...
  • ae281b4 Missing property for writable stack trace in bulk config properties (#1159)
  • 2e8e25d Updates the ReadMe to replace maxWaitTime with maxWaitDuration for BulkheadCo...
  • 70b00e5 Bump org.jetbrains.kotlin.jvm from 1.4.0 to 1.4.10
  • Additional commits viewable in compare view


Updates resilience4j-retry from 1.5.0 to 1.6.0

Release notes

Sourced from resilience4j-retry's releases.

Release v1.6.0

Enhancements

  • RetryConfig.DEFAULT_MAX_ATTEMPTS should be public #1180
  • Circuitbreaker doesn't open when nested TimeLimiter throws TimeOutCancellationException #1123
  • Enhance Server Side Events /circuitbreaker/events #1076
  • CallNotPermittedException should contain circuit breaker name (and possibly other information) #1062
  • Retry: Exponential backoff with constant behaviour after certain time #1044
  • Respecting the clock set in the CircuitBreakerStateMachine for detecting slow calls #734

Bugs

  • Circuit breaker stuck in HALF_OPEN state #935
  • Circuit breaker global fallback seems to not work when annotated method has more than 1 parameter #1174
  • Timelimiter metrics not calculated when using resilince4j-kotlin #1168
  • Problem with registering metrics for more than one circuit breaker #1131
  • ConcurrentModificationException warning log while consuming events #1115
  • CircuitBreakerConfig.Builder.waitDurationInOpenState() false documentation of when the function throws exception #1092
Changelog

Sourced from resilience4j-retry's changelog.

== Version 1.5.0

  • Issue #855: Updated resilience4j-spring-boot2 to 2.3.0.RELEASE
  • Issue #855: Updated resilience4j-spring-cloud2 to 2.2.2.RELEASE
  • Issue #942: Introduced new CB metric "notPermittedCalls"
  • Issue #964: Added Kotlin DSL for building *Config and *Registry classes
  • Issue #979: Added fairCallHandlingEnabled flag to BulkheadConfig which controls whether FairSync or NonfairSync should be used in the Semaphore.
  • Issue #982: Added support to configure exponential random backoff via Spring config
  • Issue #991: Fixed bug that auto transition to half_open happens even if the state is forced open.
  • Issue #1000: Added toString to CircuitBreakerConfig
  • Issue #1003: Fixed bug that CircuitBreaker tries to obtain permission twice in circuitBreaker.decorateEitherSupplier()

== Version 1.6.0

=== Enhancements

  • RetryConfig.DEFAULT_MAX_ATTEMPTS should be public #1180
  • Circuitbreaker doesn't open when nested TimeLimiter throws TimeOutCancellationException #1123
  • Enhance Server Side Events /circuitbreaker/events #1076
  • CallNotPermittedException should contain circuit breaker name (and possibly other information) #1062
  • Retry: Exponential backoff with constant behaviour after certain time #1044
  • Respecting the clock set in the CircuitBreakerStateMachine for detecting slow calls #734

=== Bugs

  • Circuit breaker stuck in HALF_OPEN state #935
  • Circuit breaker global fallback seems to not work when annotated method has more than 1 parameter #1174
  • Timelimiter metrics not calculated when using resilince4j-kotlin #1168
  • Problem with registering metrics for more than one circuit breaker #1131
  • ConcurrentModificationException warning log while consuming events #1115
  • CircuitBreakerConfig.Builder.waitDurationInOpenState() false documentation of when the function throws exception #1092
Commits
  • a0f029b Added 1.6.0 RELEASENOTES.adoc
  • 5a77b1d Issue #1044: Added maxWaitDurationInOpenState to limit CircuitBreaker exponen...
  • 49219fc Issue #1044: Added maxInterval to limit exponential backoff - spring properti...
  • 21f6cf8 Issue #1168: Map TimeoutCancellationException to TimeoutException and registe...
  • bec8535 Issue #1180: Made RetryConfig default maxAttempts public (#1184)
  • b5e5079 Issue #1171: Made configs serializable
  • 1846244 Issue #1174: Fixed issue where generic fallback methods wouldn't work for met...
  • ae281b4 Missing property for writable stack trace in bulk config properties (#1159)
  • 2e8e25d Updates the ReadMe to replace maxWaitTime with maxWaitDuration for BulkheadCo...
  • 70b00e5 Bump org.jetbrains.kotlin.jvm from 1.4.0 to 1.4.10
  • Additional commits viewable in compare view


Updates resilience4j-retrofit from 1.5.0 to 1.6.0

Release notes

Sourced from resilience4j-retrofit's releases.

Release v1.6.0

Enhancements

  • RetryConfig.DEFAULT_MAX_ATTEMPTS should be public #1180
  • Circuitbreaker doesn't open when nested TimeLimiter throws TimeOutCancellationException #1123
  • Enhance Server Side Events /circuitbreaker/events #1076
  • CallNotPermittedException should contain circuit breaker name (and possibly other information) #1062
  • Retry: Exponential backoff with constant behaviour after certain time #1044
  • Respecting the clock set in the CircuitBreakerStateMachine for detecting slow calls #734

Bugs

  • Circuit breaker stuck in HALF_OPEN state #935
  • Circuit breaker global fallback seems to not work when annotated method has more than 1 parameter #1174
  • Timelimiter metrics not calculated when using resilince4j-kotlin #1168
  • Problem with registering metrics for more than one circuit breaker #1131
  • ConcurrentModificationException warning log while consuming events #1115
  • CircuitBreakerConfig.Builder.waitDurationInOpenState() false documentation of when the function throws exception #1092
Changelog

Sourced from resilience4j-retrofit's changelog.

== Version 1.5.0

  • Issue #855: Updated resilience4j-spring-boot2 to 2.3.0.RELEASE
  • Issue #855: Updated resilience4j-spring-cloud2 to 2.2.2.RELEASE
  • Issue #942: Introduced new CB metric "notPermittedCalls"
  • Issue #964: Added Kotlin DSL for building *Config and *Registry classes
  • Issue #979: Added fairCallHandlingEnabled flag to BulkheadConfig which controls whether FairSync or NonfairSync should be used in the Semaphore.
  • Issue #982: Added support to configure exponential random backoff via Spring config
  • Issue #991: Fixed bug that auto transition to half_open happens even if the state is forced open.
  • Issue #1000: Added toString to CircuitBreakerConfig
  • Issue #1003: Fixed bug that CircuitBreaker tries to obtain permission twice in circuitBreaker.decorateEitherSupplier()

== Version 1.6.0

=== Enhancements

  • RetryConfig.DEFAULT_MAX_ATTEMPTS should be public #1180
  • Circuitbreaker doesn't open when nested TimeLimiter throws TimeOutCancellationException #1123
  • Enhance Server Side Events /circuitbreaker/events #1076
  • CallNotPermittedException should contain circuit breaker name (and possibly other information) #1062
  • Retry: Exponential backoff with constant behaviour after certain time #1044
  • Respecting the clock set in the CircuitBreakerStateMachine for detecting slow calls #734

=== Bugs

  • Circuit breaker stuck in HALF_OPEN state #935
  • Circuit breaker global fallback seems to not work when annotated method has more than 1 parameter #1174
  • Timelimiter metrics not calculated when using resilince4j-kotlin #1168
  • Problem with registering metrics for more than one circuit breaker #1131
  • ConcurrentModificationException warning log while consuming events #1115
  • CircuitBreakerConfig.Builder.waitDurationInOpenState() false documentation of when the function throws exception #1092
Commits
  • a0f029b Added 1.6.0 RELEASENOTES.adoc
  • 5a77b1d Issue #1044: Added maxWaitDurationInOpenState to limit CircuitBreaker exponen...
  • 49219fc Issue #1044: Added maxInterval to limit exponential backoff - spring properti...
  • 21f6cf8 Issue #1168: Map TimeoutCancellationException to TimeoutException and registe...
  • bec8535 Issue #1180: Made RetryConfig default maxAttempts public (#1184)
  • b5e5079 Issue #1171: Made configs serializable
  • 1846244 Issue #1174: Fixed issue where generic fallback methods wouldn't work for met...
  • ae281b4 Missing property for writable stack trace in bulk config properties (#1159)
  • 2e8e25d Updates the ReadMe to replace maxWaitTime with maxWaitDuration for BulkheadCo...
  • 70b00e5 Bump org.jetbrains.kotlin.jvm from 1.4.0 to 1.4.10
  • 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 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 - `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)