search

TheRandomLabs / CurseAPI

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

Bump resilience4jVersion from 1.3.0 to 1.3.1 #21

Closed dependabot-preview[bot] closed 4 years ago

dependabot-preview[bot] commented 4 years ago

Bumps resilience4jVersion from 1.3.0 to 1.3.1. Updates resilience4j-circuitbreaker from 1.3.0 to 1.3.1

Release notes

Sourced from resilience4j-circuitbreaker's releases.

Release v1.3.1

  • Issue #596: Fixed a bug: The fallback method is not invoked when using CompletableFutures and a ThreadPoolBulkhead annotation in Spring Boot
Changelog

Sourced from resilience4j-circuitbreaker'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
  • ddecb4f Release version 1.3.1
  • 79378fb Issue #596: The Spring Boot fallback method is not invoked when a BulkheadFul...
  • f7d2466 Update README.adoc
  • ce32fff Update README.adoc
  • 80b632a Propagate clock into CircuitBreakerMetrics to allow mocked time-based tests. ...
  • eb01c07 Update README.adoc
  • 4ea29fd Updated version to 1.4.0-SNAPSHOT
  • 6f9b402 Release version 1.3.0
  • See full diff in compare view


Updates resilience4j-retry from 1.3.0 to 1.3.1

Release notes

Sourced from resilience4j-retry's releases.

Release v1.3.1

  • Issue #596: Fixed a bug: The fallback method is not invoked when using CompletableFutures and a ThreadPoolBulkhead annotation in Spring Boot
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
  • ddecb4f Release version 1.3.1
  • 79378fb Issue #596: The Spring Boot fallback method is not invoked when a BulkheadFul...
  • f7d2466 Update README.adoc
  • ce32fff Update README.adoc
  • 80b632a Propagate clock into CircuitBreakerMetrics to allow mocked time-based tests. ...
  • eb01c07 Update README.adoc
  • 4ea29fd Updated version to 1.4.0-SNAPSHOT
  • 6f9b402 Release version 1.3.0
  • See full diff in compare view


Updates resilience4j-retrofit from 1.3.0 to 1.3.1

Release notes

Sourced from resilience4j-retrofit's releases.

Release v1.3.1

  • Issue #596: Fixed a bug: The fallback method is not invoked when using CompletableFutures and a ThreadPoolBulkhead annotation in Spring Boot
Changelog

Sourced from resilience4j-retrofit'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
  • ddecb4f Release version 1.3.1
  • 79378fb Issue #596: The Spring Boot fallback method is not invoked when a BulkheadFul...
  • f7d2466 Update README.adoc
  • ce32fff Update README.adoc
  • 80b632a Propagate clock into CircuitBreakerMetrics to allow mocked time-based tests. ...
  • eb01c07 Update README.adoc
  • 4ea29fd Updated version to 1.4.0-SNAPSHOT
  • 6f9b402 Release version 1.3.0
  • 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 - `@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)