Skip to content

chore(deps): update core handwritten gems lockfiles#34747

Open
renovate-bot wants to merge 1 commit into
googleapis:mainfrom
renovate-bot:renovate/core-handwritten-gems-lockfiles
Open

chore(deps): update core handwritten gems lockfiles#34747
renovate-bot wants to merge 1 commit into
googleapis:mainfrom
renovate-bot:renovate/core-handwritten-gems-lockfiles

Conversation

@renovate-bot

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
google-apis-core (source, changelog) 0.11.30.18.0 age confidence
google-cloud-bigquery-connection-v1 ">= 1.3.0", "< 1.5"">= 1.3.0", "< 1.7.1" age confidence
google-style "~> 1.30.0""~> 1.32.0" age confidence
google-style "~> 1.25.1""~> 1.32.0" age confidence
google-style "~> 1.31.1""~> 1.32.0" age confidence
google-style "~> 1.30.1""~> 1.32.0" age confidence
minitest-autotest 1.2.01.2.2 age confidence
minitest-reporters "~> 1.5.0""~> 1.8.0" age confidence
minitest-reporters "~> 1.7.0""~> 1.8.0" age confidence
ostruct (changelog) "~> 0.5.5""~> 0.6.0" age confidence
pry "~> 0.15.2""~> 0.16.0" age confidence
retriable "~> 3.1.2""~> 3.8.0" age confidence

Release Notes

googleapis/google-api-ruby-client (google-apis-core)

v0.18.0

Compare Source

Features
  • Restart & delete resumable upload (#​21896)

v0.17.0

Compare Source

Features
Bug Fixes
  • Fixed a method redefined warning (#​21572)
  • Ensure compatibility with frozen string literals (#​21648)

v0.16.0

Features
  • add ECONNRESET error as retriable error (#​20354)

v0.15.1

Bug Fixes

v0.15.0

Compare Source

Features
  • Introduce api_version to discovery clients (#​18969)

v0.14.1

Compare Source

Bug Fixes
  • fixes uninitialized Pathname issue (#​18480)

v0.14.0

Compare Source

Features
  • Update minimum Ruby version to 2.7 (#​17896)
Bug Fixes
  • allow BaseService#root_url to be an Addressable::URI (#​17895)

v0.13.0

Compare Source

Features
  • Verify credential universe domain against configured universe domain (#​17569)

v0.12.0

Compare Source

Features
googleapis/google-cloud-ruby (google-cloud-bigquery-connection-v1)

v1.7.0: google-cloud-bigquery-connection-v1: v1.7.0

1.7.0 (2026-06-11)
Features
  • update gapic-common dependency to 1.3 and document retry jitter (#​34040)

v1.6.0: google-cloud-bigquery-connection-v1: v1.6.0

1.6.0 (2026-04-02)
Features
  • publish client batch config schema (#​33430)

v1.5.0: google-cloud-bigquery-connection-v1: v1.5.0

1.5.0 (2026-03-19)
Features
  • Upgrade dependencies for Ruby v4.0 and drop Ruby v3.1 support
googleapis/ruby-style (google-style)

v1.32.0

Features
  • Update TargetRubyVersion to 3.2 (#​98)

v1.31.1

Bug Fixes
  • rename cop to eliminate extra warnings (#​90)

v1.31.0

Features
  • update ruby version, audit some cops (#​88)
seattlerb/minitest-autotest (minitest-autotest)

v1.2.2

Compare Source

v1.2.1

Compare Source

minitest-reporters/minitest-reporters (minitest-reporters)

v1.8.0

Compare Source

  • Added support for minitest 6 #​366 contributed by Maimer
  • Updated gemspec to avoid packaging unnecessary files in the gem

v1.7.1

Compare Source

  • Fixed logic of new suppress_inline_failure_output. This option was doing the opposite of what it intended to do.
    #​354

v1.7.0

Compare Source

  • Minor documentation improvements #​343
  • Fixed homepage link in gemspec #​333 contributed by andyw8
  • Added Ruby 3.2 to the CI matrix #​335 contributed by petergoldstein
  • Updated JUnitReporter to output a failure screenshot path when included in the minitest result #​346 contributed by matteeyah
  • Fixed backwards fraction in ProgressReporter default format #​348 contributed by notEthan
  • Added option suppress_inline_failure_output to SpecReporter to provide an explicit switch, separate from print_failure_summary, for suppressing inline failure messages. Until this change, the print_failure_summary would do both: print a failure/error summary after all tests run and suppress the inline failure messages. With this change print_failure_summary will just add a summary at the end of a test run, and it will no longer suppress the inline failure messages. #​352 contributed by rthbound

v1.6.1

Compare Source

  • Replaced use of MiniTest constant with Minitest #​345 contributed by istana

v1.6.0

Compare Source

  • Switched to Github actions #​324 petergoldstein
  • Fixed misspelled method name in HTML reporter (percent_skipps -> percent_skips) #​326 contributed by andyw8
  • Removed deprecated call to Object#=~ #​318 contributed by etiennebarrie
  • Added option print_failure_summary to SpecReporter which causes failures and errors to print at the end of the test suite instead of inline
    as they happen #​306 contributed by picandocodigo
ruby/ostruct (ostruct)

v0.6.3

Compare Source

What's Changed

Full Changelog: ruby/ostruct@v0.6.2...v0.6.3

v0.6.2

Compare Source

What's Changed

New Contributors

Full Changelog: ruby/ostruct@v0.6.1...v0.6.2

v0.6.1

Compare Source

What's Changed

Full Changelog: ruby/ostruct@v0.6.0...v0.6.1

v0.6.0

Compare Source

What's Changed
New Contributors

Full Changelog: ruby/ostruct@v0.5.5...v0.6.0

kamui/retriable (retriable)

v3.8.0

Compare Source

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

Compare Source

  • 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

Compare Source

  • 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

Compare Source

  • 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.

v3.5.1

Compare Source

  • Fix: Validate retry timing and count options before use to reject invalid retry configurations. tries must now be a positive integer unless a custom intervals array is provided.

v3.5.0

Compare Source

  • Fix: Do not count skipped sleep intervals against max_elapsed_time when sleep_disabled is true.
  • Add override and reset_override APIs to force retry settings over local call options when needed (for example, test short-circuiting).

v3.4.1

Compare Source

  • Fix: Use Process.clock_gettime(CLOCK_MONOTONIC) for elapsed time tracking so retry timing is immune to wall-clock adjustments (NTP, manual changes).
  • Fix: Handle max_elapsed_time: nil gracefully instead of raising NoMethodError.
  • Remove dead * 1.0 float coercion in ExponentialBackoff#randomize.

v3.4.0

Compare Source

  • Add retry_if option to support custom retry predicates, including checks against wrapped exception.cause values.

v3.3.0

Compare Source

  • Refactor Retriable.retriable internals into focused private helpers to improve readability while preserving behavior.
  • Modernize .rubocop.yml with explicit modern defaults to enable new cops while preserving existing project style policies.

v3.2.1

Compare Source

  • Remove executables from gemspec as it was polluting the path for some users. Thanks @​hsbt.

v3.2.0

Compare Source

  • Require ruby 2.3+.
  • Fix: Ensure tries value is overridden by intervals parameter if both are provided and add a test for this. This is always what the README stated but the code didn't actually do it.
  • Fix: Some rubocop offenses.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate-bot renovate-bot requested review from a team and yoshi-approver as code owners July 10, 2026 18:09
@trusted-contributions-gcf trusted-contributions-gcf Bot added kokoro:force-run Add this label to force Kokoro to re-run the tests. owlbot:run Add this label to trigger the Owlbot post processor. labels Jul 10, 2026
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jul 10, 2026
@gcf-owl-bot gcf-owl-bot Bot removed the owlbot:run Add this label to trigger the Owlbot post processor. label Jul 10, 2026
@torreypayne torreypayne added the do not merge Indicates a pull request not ready for merge, due to either quality or timing. label Jul 10, 2026
@renovate-bot renovate-bot force-pushed the renovate/core-handwritten-gems-lockfiles branch from 22c62a2 to 350f87e Compare July 10, 2026 21:22
@trusted-contributions-gcf trusted-contributions-gcf Bot added kokoro:force-run Add this label to force Kokoro to re-run the tests. owlbot:run Add this label to trigger the Owlbot post processor. labels Jul 10, 2026
@gcf-owl-bot gcf-owl-bot Bot removed the owlbot:run Add this label to trigger the Owlbot post processor. label Jul 10, 2026
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jul 10, 2026
@torreypayne torreypayne removed the do not merge Indicates a pull request not ready for merge, due to either quality or timing. label Jul 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants