build(deps): bump retriable from 3.5.1 to 3.8.0

[dependabot]

Bumps retriable from 3.5.1 to 3.8.0.

Release notes

Sourced from retriable's releases.

v3.8.0

3.8.0

Deprecations

• Deprecated the timeout: option ahead of its removal in Retriable 4.0. Non-nil timeout values supplied through Retriable.configure, Retriable.retriable(...), or Retriable.with_override(...) now emit a deprecation warning while keeping the existing runtime behavior unchanged. On Ruby 2.7+ the warning is emitted via Kernel.warn(..., category: :deprecated), so callers can silence it through the standard Ruby controls (Warning[:deprecated] = false, ruby -W:no-deprecated, or a custom Warning.warn). To keep the notice from drowning busy applications, it is emitted at most once per process; suppression via Warning[:deprecated] leaves the warner armed for the next call that re-enables the category. Prefer library-native timeout settings, or wrap the retried block in Timeout.timeout(...) directly if you still need that behavior. See the README migration guidance for details.

v3.7.0

3.7.0

• Feature: Opt-in unbounded retries via tries: Float::INFINITY. Requires a finite max_elapsed_time as a safety bound and is incompatible with custom intervals:. Both invalid configurations raise ArgumentError from Config#validate!.

v3.6.1

3.6.1

• Fix: Validate the on: option before retrying. Previously, passing a non-Exception value such as Object, Kernel, or a plain Module (which appear in every Exception's ancestor chain) would silently retry process-critical exceptions like SystemExit and Interrupt. The on: option now requires an Exception subclass, an array of them, or a hash whose keys are such classes and whose values are nil, a Regexp, or an array of Regexps. Invalid shapes raise ArgumentError before the block runs.
• Fix: Validate with_override(contexts:) shape before applying overrides. contexts may be nil or a hash, and each per-context override must be a hash.
• Docs: Document that on_retry: false disables a callback set in Retriable.configure for a single call.

v3.6.0

3.6.0

• Breaking: Retriable.override and Retriable.reset_override are removed and replaced by block-scoped Retriable.with_override(opts) { ... }. The new API requires a block, restores the previous override (or absence of override) when the block exits via ensure, and is thread-local — overrides set in one thread do not affect other threads, and child threads do not inherit them. Fibers within a thread still share the thread's active override. Nested with_override calls correctly restore the outer override on inner exit. See the README and docs/testing.md for migration and testing patterns. This replaces the override API introduced in 3.5.0.

Changelog

Sourced from retriable's changelog.

3.8.0

Deprecations

• Deprecated the timeout: option ahead of its removal in Retriable 4.0. Non-nil timeout values supplied through Retriable.configure, Retriable.retriable(...), or Retriable.with_override(...) now emit a deprecation warning while keeping the existing runtime behavior unchanged. On Ruby 2.7+ the warning is emitted via Kernel.warn(..., category: :deprecated), so callers can silence it through the standard Ruby controls (Warning[:deprecated] = false, ruby -W:no-deprecated, or a custom Warning.warn). To keep the notice from drowning busy applications, it is emitted at most once per process; suppression via Warning[:deprecated] leaves the warner armed for the next call that re-enables the category. Prefer library-native timeout settings, or wrap the retried block in Timeout.timeout(...) directly if you still need that behavior. See the README migration guidance for details.

3.7.0

• Feature: Opt-in unbounded retries via tries: Float::INFINITY. Requires a finite max_elapsed_time as a safety bound and is incompatible with custom intervals:. Both invalid configurations raise ArgumentError from Config#validate!.

3.6.1

• Fix: Validate the on: option before retrying. Previously, passing a non-Exception value such as Object, Kernel, or a plain Module (which appear in every Exception's ancestor chain) would silently retry process-critical exceptions like SystemExit and Interrupt. The on: option now requires an Exception subclass, an array of them, or a hash whose keys are such classes and whose values are nil, a Regexp, or an array of Regexps. Invalid shapes raise ArgumentError before the block runs.
• Fix: Validate with_override(contexts:) shape before applying overrides. contexts may be nil or a hash, and each per-context override must be a hash.
• Docs: Document that on_retry: false disables a callback set in Retriable.configure for a single call.

3.6.0

• Breaking: Retriable.override and Retriable.reset_override are removed and replaced by block-scoped Retriable.with_override(opts) { ... }. The new API requires a block, restores the previous override (or absence of override) when the block exits via ensure, and is thread-local — overrides set in one thread do not affect other threads, and child threads do not inherit them. Fibers within a thread still share the thread's active override. Nested with_override calls correctly restore the outer override on inner exit. See the README and docs/testing.md for migration and testing patterns. This replaces the override API introduced in 3.5.0.

Commits

• 0167ed6 Update installation instruction in README to reference 3.8
• 3c6ffa7 Deprecate timeout option for 3.8.0 (#135)
• 34fcffa Add unbounded retries with Float::INFINITY (#133)
• de63029 Remove doc file that wasn't supposed to be commit
• 8d82a3e Add design doc for on_give_up callback follow-ups (issue #72, PR #127)
• 46c23f9 Add override validation state specs
• 5deeda6 Validate with_override contexts shape (#132)
• fa6179a Document on_retry: false sentinel for disabling configured callback (#131)
• 3cdfb05 Validate on: option against non-Exception values (#129)
• 250612f docs: add README table of contents (#130)
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)