Skip to content

build(deps): bump the most-gems group with 21 updates - #1324

Open
dependabot[bot] wants to merge 2 commits into
mainfrom
dependabot/bundler/most-gems-75c80b2174
Open

build(deps): bump the most-gems group with 21 updates#1324
dependabot[bot] wants to merge 2 commits into
mainfrom
dependabot/bundler/most-gems-75c80b2174

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 1, 2026

Copy link
Copy Markdown
Contributor

Bumps the most-gems group with 21 updates:

Package From To
httpx 1.8.0 1.8.1
simplecov 0.22.0 1.0.2
yard 0.9.44 0.9.45
aws-sdk-lambda 1.186.0 1.191.0
aws-sdk-sqs 1.116.0 1.117.0
aws-sdk-cloudwatch 1.141.0 1.145.0
aws-sdk-s3 1.226.0 1.228.1
async 2.41.0 2.43.0
aws-partitions 1.1262.0 1.1273.0
aws-sdk-core 3.252.0 3.254.0
aws-sdk-kms 1.129.0 1.130.0
concurrent-ruby 1.3.7 1.3.8
console 1.36.0 1.37.0
erb 6.0.4 6.0.6
http-2 1.2.0 1.2.1
io-event 1.17.0 1.19.3
json 2.20.0 2.21.1
language_server-protocol 3.17.0.5 3.17.0.6
parser 3.3.11.1 3.3.12.0
rubocop-ast 1.49.1 1.50.0
sass-embedded 1.101.0 1.102.0

Updates httpx from 1.8.0 to 1.8.1

Commits
  • 988e6c2 bump version to 1.8.1
  • 60b9b0b Revert "revert max retries conf"
  • 66ce00b changed test of ssrf filter exception to remove mention of public/private (al...
  • 58aa9cd revert max retries conf
  • 8b0fc4a fixed the test fiber scheduler to accomodate the cases being tested
  • 31ab58a Merge branch 'fix-timers' into 'master'
  • 7e367b6 temporarily patch fiber scheduler tests
  • b6d72cd do not allow connection idle/closed transitions if there ain't no more requests
  • 549368e fix simplecov conf v1 deprecations
  • ac3c698 correctly clearing timers across the request lifecycle
  • Additional commits viewable in compare view

Updates simplecov from 0.22.0 to 1.0.2

Release notes

Sourced from simplecov's releases.

v1.0.2

What's Changed

Full Changelog: simplecov-ruby/simplecov@v1.0.1...v1.0.2

v1.0.1

What's Changed

New Contributors

Full Changelog: simplecov-ruby/simplecov@v1.0.0...v1.0.1

v1.0.0

What's Changed

... (truncated)

Changelog

Sourced from simplecov's changelog.

1.0.2 (2026-07-18)

Bugfixes

  • The standalone simplecov CLI's colorizing subcommands (report, uncovered, coverage, diff) no longer crash with NoMethodError: undefined method 'color' when run in a project without a .simplecov file. The CLI deliberately loads only simplecov/cli rather than the full library, so SimpleCov.color was undefined unless a dotfile load had incidentally defined it — and --no-color was the only workaround, since the documented NO_COLOR env var was checked after the line that raised. Color.enabled? now treats missing configuration the same as its :auto default and falls through to NO_COLOR / FORCE_COLOR / TTY detection. Reported with an exemplary diagnosis by @​hasghari. See #1231.
  • Branch tuples synthesized for tracked-but-unloaded files now match Ruby's Coverage for a safe-navigation call that takes a block. For x&.foo { ... } (and the second link of a chain like x&.foo&.bar { ... }) the extractor keyed the branch on the call node's full source range, which extends through the attached block, while Coverage ends the range at the call itself — so a simulated entry merging with a real one produced a phantom, permanently-missed branch, the same failure mode as the elsif fix in 1.0.1. Reported with an exemplary diagnosis and a suggested fix by @​alexdeng-mp. See #1233.
  • Prompted by the two reports above, an exhaustive differential audit of StaticCoverageExtractor against Ruby's Coverage — a fuzzing harness that runs thousands of generated programs through both and diffs the branch tuples, now part of the spec suite (opt-in via SIMPLECOV_FUZZ=1) — surfaced and fixed four more mismatches of the same phantom-branch class. Conditions that are compile-time literals (if true, if 1, a ternary on a literal) are folded away by Ruby's compiler and no longer produce synthesized branches (while true still does — loops are not folded). On Ruby 3.3, three legacy conventions now match: the body range of a do-while (begin ... end while), the location of empty branch arms (which on 3.3 depends on whether the construct is in value or void position), and one-line pattern matching (x => pattern / x in pattern), which emits a :case branch on 3.3 and nothing on 3.4+. The audit also caught a crash on Ruby 3.3's stdlib Prism (0.19), which still exposes the else clause of UnlessNode / CaseNode / CaseMatchNode under its pre-1.3 name consequent: the extractor raised internally and silently dropped simulated branch and method data for any file containing unless/else or a case with an empty arm, unless a newer prism gem happened to be installed.
  • As a defensive layer against any future extractor drift, merging now treats an actually-executed file's branch and method data as authoritative: when a resultset that merely tracked a file (with simulated, statically-derived tuples) merges with one from a process that really loaded it, the synthesized tuples are dropped rather than unioned. This contains any undiscovered mismatch to denominator inflation on files no process loaded, instead of phantom misses on fully-covered ones. Line coverage still combines from both sides, so tracked-but-unloaded files keep contributing to the line denominator as before.
  • Method coverage no longer reports phantom uncovered methods for define_method / define_singleton_method blocks defined onto more than one receiver — e.g. a module's included hook defining the same block on every including class. Ruby records one method entry per receiver, all pointing at the same source location, so any receiver whose copy was never called showed as an uncovered method on a line with 100% line coverage. Entries are now aggregated by (name, source location) with hit counts summed, and cross-process merging matches methods on the same source identity rather than on the receiver class. Reported with an exemplary diagnosis by @​bkuhlmann. See #1234.
  • Branch coverage under enable_coverage :eval no longer inflates denominators or reports phantom missed branches for templates compiled more than once — e.g. hanami-view compiles each template once per view class, and every ERB.new(...).result is a fresh compile. Ruby's Coverage emits a fresh set of branch entries per compile of the same file (nondeterministically through Ruby 4.0, consistently on current ruby master — see https://bugs.ruby-lang.org/issues/22203), each counting only the renders that flowed through that compile, so a side exercised under one compile appeared as a permanently-missed branch in another compile's entry at the same location, and ignore_branches :implicit_else swung the report wildly by stripping only the synthetic-else halves of the duplicates. Duplicated conditions are now aggregated by source location with arm counts summed. Reported with an exemplary diagnosis by @​bkuhlmann. See #1235.

1.0.1 (2026-07-14)

Enhancements

  • The gem now ships type signatures under sig/, covering the public API: the configuration DSL (including the criterion-scoped coverage block and the legacy deprecated verbs), the Result / FileList / SourceFile / CoverageStatistics read API that formatter authors consume, the formatter and filter class hierarchies, exit codes, and the ParallelAdapters::Base contract. Internal classes carry repository-only skeleton signatures (sig/internal/, excluded from the gem package) so the entire codebase type-checks under Steep in strict mode, while the shipped signature payload stays small. Signatures are checked with rbs validate and steep check as part of the default rake task. RBS and Steep users no longer need the third-party signatures from ruby/gem_rbs_collection, which cover the 0.22 API and predate 1.0's configuration redesign.

Bugfixes

  • Branch tuples synthesized for tracked-but-unloaded files now match Ruby's Coverage exactly for elsif and for if arms with empty bodies. StaticCoverageExtractor attributed the outer else arm of an elsif to the clause's body rather than the whole clause, and an empty if then-body to the whole node rather than Coverage's zero-width point at the predicate's end. Since resultset merges combine branch arms by their exact location, a simulated entry merging with a real one for the same file (parent and worker under Minitest's parallelize, or RSpec and Minitest suites collated together) produced phantom, permanently-missed branch arms. A new differential spec now pins every branch construct tuple-for-tuple against Ruby's Coverage — which promptly caught that CRuby 3.4 changed several of these conventions, so the extractor now emits whichever shape the running Ruby's Coverage uses (on 3.2/3.3: elsif clause ranges end at the chain's last content rather than the shared end, empty if/else/when bodies fall back to enclosing ranges, and empty while/in bodies collapse to points). Reported with an exemplary diagnosis by @​hasghari. See #1226.
  • merge_subprocesses no longer silently drops all worker coverage under Minitest's fork-based parallelize(workers: N) (the setup the rails profile exists for). When Minitest's autorun was armed before SimpleCov.start — which is how rails test loads — SimpleCov deferred its report to Minitest.after_run, and forked workers inherited that deferral even though Minitest pins its after_run hook to the parent's pid, so no exit path in the worker ever stored its resultset. Workers now reset the inherited at_exit state on fork and re-arm their own hook, so their resultsets are stored and merged as documented. Reported with an exemplary diagnosis by @​hasghari. See #1227.
  • Fixed SimpleCov.formatters= raising NoMethodError when given a single formatter instead of an Array — a regression from 0.22.x, where MultiFormatter.new normalized the value internally. This restores the long-documented SimpleCov.formatters = SimpleCov::Formatter::MultiFormatter.new([...]) pattern, in which MultiFormatter.new returns a Class rather than an Array. The regression surfaced in ruby/ruby's CI through net-imap's test helper. Thanks @​koic. See #1224.
  • Formatter status lines ("Coverage report generated for X") and threshold-enforcement output (violation reports, "SimpleCov failed with exit N") no longer route through Kernel#warn. They still print to stderr, but they are program output rather than Ruby warnings, so Warning.warn hooks — warning trackers and raise-on-warning test setups — no longer intercept them as unaddressable noise, and threshold failure explanations now survive ruby -W0, which previously reduced a failing check to a bare exit code with no explanation. Genuine warnings (deprecations, dropped-file notices, parse failures) still use warn. Suppression remains explicit: silent: true for formatter status lines, print_errors false for enforcement output. Thanks @​viralpraxis. See #1225.

1.0.0 (2026-07-12)

First stable release of the 1.0 line. The entries below consolidate release candidates rc1 through rc5 and describe all changes since 0.22.1.

Breaking Changes

  • Dropped support for Ruby 3.1 and JRuby 9.4. The minimum is now Ruby 3.2 (and JRuby 10, which reports RUBY_VERSION 3.4). Ruby 3.1 reached end of life in March 2025, and a recent i18n release calls Fiber[], a Ruby 3.2 API, at load time, so suites that load Rails no longer run on 3.1. Raising required_ruby_version to >= 3.2 also excludes JRuby 9.4, which reports RUBY_VERSION 3.1.x. See #1171.
  • JSON formatter: group stats changed from { "covered_percent": 80.0 } to full stats shape { "covered": 8, "missed": 2, "total": 10, "percent": 80.0, "strength": 0.0 }. The key covered_percent is renamed to percent.
  • JSON formatter: simplecov_json_formatter gem is now built in. require "simplecov_json_formatter" continues to work via a shim.
  • StringFilter now matches at path-segment boundaries. "lib" matches /lib/ but no longer matches /library/. Use a Regexp filter for substring matching.
  • SourceFile#project_filename now returns a truly relative path with no leading separator (e.g. lib/foo.rb instead of /lib/foo.rb). This also removes the leading / from file path keys in coverage.json and from the filename in minimum_coverage_by_file error messages. Anchored RegexFilters that relied on a leading / (e.g. %r{^/lib/}) should be rewritten (e.g. %r{\Alib/}).
  • Removed docile gem dependency. The SimpleCov.configure block is now evaluated via instance_exec with instance variable proxying.
  • Removed automatic activation of JSONFormatter when the CC_TEST_REPORTER_ID environment variable is set. The default HTMLFormatter now emits coverage.json alongside the HTML report (using JSONFormatter.build_hash to serialize the same payload JSONFormatter writes), so the env-var special case is no longer needed. Because of this, listing JSONFormatter alongside HTMLFormatter is redundant and can be removed.
  • SimpleCov.start now loads the test_frameworks profile by default, which filters paths under test/, spec/, features/, and autotest/. Running the suite always executes 100% of the test files themselves, which inflated the overall percentage and obscured application coverage. To opt back in (e.g. to surface dead test helpers), drop the filter with remove_filter %r{\A(test|features|spec|autotest)/}. See #816.
  • HTML and JSON formatters now write the "Coverage report generated for X to Y" status line (and the per-criterion totals beneath it) to stderr instead of stdout. The message is a diagnostic, not the program's output, and routing it to stdout polluted pipelines like rspec -f json. Suppress it entirely with silent: true on the formatter; redirect with 2>&1 if you want the old behavior. See #1060.
  • Under parallel_tests, SimpleCov now waits in the first started process (via ParallelTests.first_process?) rather than the last. This matches the convention parallel_tests's own README recommends for "do something once after all workers finish" hooks, so user code that has its own ParallelTests.wait_for_other_processes_to_finish in an RSpec.after(:suite) (or equivalent) no longer deadlocks against SimpleCov's wait when both pick the same process. As a side benefit, the previous PARALLEL_TEST_GROUPS=1 workaround for last_process?'s "" == "1" mismatch (#1066) is no longer needed — first_process? handles that case naturally. Migration: the rare project that wired its own wait via ParallelTests.last_process? now hits the symmetric deadlock and must switch to first_process?. See #922.
  • Removed SimpleCov.coverage_criterion. It was a reader/writer for a value nothing in SimpleCov ever consumed, so it duplicated primary_coverage without affecting any behavior. Use primary_coverage to choose the report's leading criterion (or the coverage :branch, primary: true form).

Deprecations

  • The configuration API has been redesigned around a smaller, more consistent set of verbs. The legacy methods continue to work but each emits a deprecation warning that names its replacement; a future release will remove them. Warnings are deduplicated by call site, so a deprecated method called in a loop or a configuration block re-evaluated once per parallel worker or spec file warns at most once per source location (see #1204). See the "Migrating from the legacy configuration API" section in the README for the full migration table and a before/after example.
    • add_filter → skip (identical matcher grammar; no behavior change)
    • add_group → group (identical matcher grammar; no behavior change)
    • track_files → cover (cover includes unloaded files like track_files did and restricts the report to the matching set; pass every directory you want reported, e.g. cover "lib/**/*.rb", "app/**/*.rb", to keep the old additive-only behavior)
    • use_merging → merging (same value)
    • enable_for_subprocesses → merge_subprocesses (same value)
    • enable_coverage_for_eval → enable_coverage :eval (folds into the same call that enables :line / :branch / :method)
    • print_error_status (reader) → print_errors (the print_error_status= writer is unaffected for now)

... (truncated)

Commits
  • 803dcbc Bump version to 1.0.2
  • 177b0cc Restore a clean Steep check for the post-1.0.1 code
  • b57bf8d Aggregate runtime-duplicated coverage entries by source location
  • 9599343 Drop a simulated file's branches when a real run covered it
  • 25d1ab5 Add a differential fuzzer for the static coverage extractor
  • 2aff8fe Match Coverage's legacy branch conventions and survive stdlib Prism
  • bbb4737 Skip synthesizing branches for constant-folded conditions
  • 6669cbf Match Coverage's safe-navigation range when the call takes a block
  • 21a8a08 Fix NoMethodError in the standalone CLI's colorizing subcommands
  • e27cfd0 Bump step-security/harden-runner from 2.19.4 to 2.20.0
  • Additional commits viewable in compare view

Updates yard from 0.9.44 to 0.9.45

Release notes

Sourced from yard's releases.

Release v0.9.45

  • Use @param types to document generated Struct.new and Data.define members (#1684)
  • Add compatibility with RDoc 8
  • Fix TypesExplainer parsing of types following Hash collections (#1688)
  • Fix HTML generation for RBS constants without source values (#1686)
  • Fix method redefinition warnings when loading YARD with Ruby warnings enabled (#1687)
  • Improve sanitization of yard server request paths
Changelog

Sourced from yard's changelog.

0.9.45 - July 14th, 2026

  • Use @param types to document generated Struct.new and Data.define members (#1684)
  • Add compatibility with RDoc 8
  • Fix TypesExplainer parsing of types following Hash collections (#1688)
  • Fix HTML generation for RBS constants without source values (#1686)
  • Fix method redefinition warnings when loading YARD with Ruby warnings enabled (#1687)
  • Improve sanitization of yard server request paths
Commits
  • 2659ecd Release: v0.9.45
  • 2b467e0 Create a gh-fix skill
  • 2842ba7 Update changelog
  • 00fe9b1 Refactor server sanitization logic
  • c6fd371 Use @​param types for Struct and Data members (#1695)
  • d2a8883 Merge remote-tracking branch 'origin/main' into fix/issue-1684-struct-data-pa...
  • 674d0cf Fix parser method redefinition warnings (#1694)
  • 9483cd3 Use param types for Struct and Data members
  • 12ed8b7 Merge main into fix/issue-1687-method-redefined-warnings
  • 9b874e2 Fix HTML generation for RBS constants
  • Additional commits viewable in compare view

Updates aws-sdk-lambda from 1.186.0 to 1.191.0

Changelog

Sourced from aws-sdk-lambda's changelog.

1.191.0 (2026-07-14)

  • Feature - AWS Lambda now returns a new DependencyError value in StateReasonCode and LastUpdateStatusReasonCode to provide more actionable information when a function reaches a failed state due to an error from an upstream dependency or service.

1.190.0 (2026-07-13)

  • Feature - Add Java 8, 11 and 17 on AL2023 (java8.al2023, java11.al2023, java17.al2023) support to AWS Lambda.

1.189.0 (2026-07-10)

  • Feature - Added TelemetryConfig support for Managed Instances Capacity Provider, enabling customers to configure system log level and custom log group for managed instance logging.

1.188.0 (2026-07-09)

  • Feature - Code Generated Changes, see ./build_tools or aws-sdk-core's CHANGELOG.md for details.

1.187.0 (2026-07-07)

  • Feature - AWS Lambda Durable Functions now supports customer managed KMS keys. This allows customers to configure a KMS key in Durable Config to have all their durable execution data encrypted.
Commits

Updates aws-sdk-sqs from 1.116.0 to 1.117.0

Changelog

Sourced from aws-sdk-sqs's changelog.

1.117.0 (2026-07-09)

  • Feature - Code Generated Changes, see ./build_tools or aws-sdk-core's CHANGELOG.md for details.
Commits

Updates aws-sdk-cloudwatch from 1.141.0 to 1.145.0

Changelog

Sourced from aws-sdk-cloudwatch's changelog.

1.145.0 (2026-07-22)

  • Feature - Adds documented value constraints for CloudWatch Log Alarm scheduled query configuration fields, and makes LogGroupIdentifiers optional for log alarms.

1.144.0 (2026-07-10)

  • Feature - CloudWatch now assigns a unique identifier to each anomaly detector. PutAnomalyDetector and DescribeAnomalyDetectors return this AnomalyDetectorId, which you can use to describe or delete a specific anomaly detector directly.

1.143.0 (2026-07-09)

  • Feature - Code Generated Changes, see ./build_tools or aws-sdk-core's CHANGELOG.md for details.

1.142.0 (2026-06-30)

  • Feature - Customers can configure alarms with wall-clock-aligned evaluation windows instead of sliding windows, with optional timezone support for daily or weekly periods
Commits

Updates aws-sdk-s3 from 1.226.0 to 1.228.1

Changelog

Sourced from aws-sdk-s3's changelog.

1.228.1 (2026-07-23)

  • Issue - Ensure the source file is closed on multipart upload_file part failure, preventing leaked file descriptors (#3408).

1.228.0 (2026-07-16)

  • Feature - Documentation update for removing the 30 day minimum restriction for transition to Standard-IA or OneZone-IA storage classes

1.227.0 (2026-07-09)

  • Feature - Code Generated Changes, see ./build_tools or aws-sdk-core's CHANGELOG.md for details.
Commits

Updates async from 2.41.0 to 2.43.0

Release notes

Sourced from async's releases.

v2.43.0

  • Propagate cancellation causes through task trees so child tasks observe the original cancellation cause.

v2.42.0

  • Sync and Async can now be invoked from a non-blocking fiber that has no scheduler (e.g. inside an Enumerator or a bare Fiber.new). Previously this raised RuntimeError: Running scheduler on non-blocking fiber!. The reactor is now run within Fiber.blocking, so the scheduler always runs on a blocking fiber.
Changelog

Sourced from async's changelog.

v2.43.0

  • Propagate cancellation causes through task trees so child tasks observe the original cancellation cause.

v2.42.0

  • Sync and Async can now be invoked from a non-blocking fiber that has no scheduler (e.g. inside an Enumerator or a bare Fiber.new). Previously this raised RuntimeError: Running scheduler on non-blocking fiber!. The reactor is now run within Fiber.blocking, so the scheduler always runs on a blocking fiber.
Commits

Updates aws-partitions from 1.1262.0 to 1.1273.0

Changelog

Sourced from aws-partitions's changelog.

1.1273.0 (2026-07-24)

  • Feature - Updated the partitions source data that determines the AWS service regions and endpoints.

1.1272.0 (2026-07-22)

  • Feature - Updated the partitions source data that determines the AWS service regions and endpoints.

1.1271.0 (2026-07-17)

  • Feature - Updated the partitions source data that determines the AWS service regions and endpoints.

1.1270.0 (2026-07-16)

  • Feature - Updated the partitions source data that determines the AWS service regions and endpoints.

1.1269.0 (2026-07-13)

  • Feature - Updated the partitions source data that determines the AWS service regions and endpoints.

1.1268.0 (2026-07-10)

  • Feature - Updated the partitions source data that determines the AWS service regions and endpoints.

1.1267.0 (2026-07-07)

  • Feature - Added support for enumerating regions for Aws::PartnerCentralRevenueMeasurement.

1.1266.0 (2026-07-06)

  • Feature - Updated the partitions source data that determines the AWS service regions and endpoints.

1.1265.0 (2026-07-02)

  • Feature - Updated the partitions source data that determines the AWS service regions and endpoints.

1.1264.0 (2026-07-01)

  • Feature - Updated the partitions source data that determines the AWS service regions and endpoints.

... (truncated)

Commits

Updates aws-sdk-core from 3.252.0 to 3.254.0

Changelog

Sourced from aws-sdk-core's changelog.

3.254.0 (2026-07-09)

  • Feature - Serialize BigDecimal values as JSON numbers in document types for REST-JSON and JSON protocols.

3.253.0 (2026-07-08)

  • Feature - Updated Aws::Signin::Client with the latest API changes.

  • Feature - Adds support for OAuth 2.0 token operations in AWS Sign-In, CreateOAuth2TokenWithIAM (client credentials flow), IntrospectOAuth2TokenWithIAM (token inspection), and RevokeOAuth2TokenWithIAM (token revocation).

Commits

Updates aws-sdk-kms from 1.129.0 to 1.130.0

Changelog

Sourced from aws-sdk-kms's changelog.

1.130.0 (2026-07-09)

  • Feature - Code Generated Changes, see ./build_tools or aws-sdk-core's CHANGELOG.md for details.
Commits

Updates concurrent-ruby from 1.3.7 to 1.3.8

Release notes

Sourced from concurrent-ruby's releases.

v1.3.8

What's Changed

New Contributors

Full Changelog: ruby-concurrency/concurrent-ruby@v1.3.7...v1.3.8

Changelog

Sourced from concurrent-ruby's changelog.

Release v1.3.8 (19 July 2026)

concurrent-ruby:

Commits
  • 0b88d5f Release 1.3.8
  • 0f83a98 Allow to use Concurrent::Map#compute_if_absent in a Ractor (#1109)
  • cc5a32f Programatically set the backtrace_location on exception:
  • See full diff in compare view

Updates console from 1.36.0 to 1.37.0

Release notes

Sourced from console's releases.

v1.37.0

  • Show compound units in elapsed time display.
Changelog

Sourced from console's changelog.

v1.37.0

  • Show compound units in elapsed time display.
Commits

Updates erb from 6.0.4 to 6.0.6

Release notes

Sourced from erb's releases.

v6.0.6

What's Changed

New Contributors

Full Changelog: ruby/erb@v6.0.5...v6.0.6

v6.0.5

What's Changed

New Contributors

Full Changelog: ruby/erb@v6.0.4...v6.0.5

Changelog

Sourced from erb's changelog.

6.0.6

  • Fix -h CLI option

6.0.5

  • Avoid overridable method dispatch in the initialization guard
Commits
  • 488683a Version 6.0.6
  • 0f9a6d6 Fix -h CLI option (#126)
  • 37daba6 Fix documentation typos and code examples (#125)
  • 37c941c Version 6.0.5
  • ce08ffb Hide ERB init guard internals from RDoc
  • 4bf35f1 Avoid dispatch in ERB initialization guard
  • fbe832a Fix wrong receiver in eoutvar example for #src (#123)
  • ba3086d Bump actions/checkout from 6 to 7
  • e559839 Add a job to aggregate test results
  • cc48728 Bump lewagon/wait-on-check-action from 1.7.0 to 1.8.0
  • Additional commits viewable in compare view

Updates http-2 from 1.2.0 to 1.2.1

Changelog

Sourced from http-2's changelog.

1.2.1

  • fix: encode the string to binary when using String#bytesplice (if the string is UTF-8 and the range would split multibyte characters, bytesplicing raises an error).
Commits
  • 07621f0 Merge pull request #191 from HoneyryderChuck/fix-bytesplice
  • bf3cdc0 bump version to 1.2.1
  • dc550fb fix String#bytesplice usage, which in order to be able to cut UTF-8 character...
  • 4f990ca remove dead code
  • See full diff in compare view

Updates io-event from 1.17.0 to 1.19.3

Release notes

Sourced from io-event's releases.

v1.19.3

  • Prevent URing, EPoll, and KQueue from entering a native wait when a signal exception becomes pending during the GVL transition. On Ruby versions without RB_NOGVL_PENDING_INTR_FAIL, the fallback now refreshes pending-interrupt state immediately before releasing the GVL while preserving the caller's exception-delivery timing.

v1.19.2

  • Use rb_process_status_for when available to construct URing process_wait results directly from waitid, avoiding the extra reap syscall previously needed to build a Process::Status.

v1.19.1

  • Fix Process.waitall / Process.detach under the URing selector: when io_uring's waitid reported an error (e.g. ECHILD when there are no more children), the process_wait hook raised instead of returning the error as a Process::Status, so callers that expect waitpid to report "no more children" rather than raise would fail.

v1.19.0

  • Use io_uring_prep_waitid for process_wait in the URing selector (Linux 6.7+), waiting for child exit directly in the ring instead of polling on a pidfd. The child is reaped via rb_process_status_wait (using WEXITED | WNOWAIT) to construct a correct Process::Status, and process_wait(-1, ...) / process_wait(0, ...) are now supported.
  • Support waiting for any child or a process group (pid <= 0) on all selectors. The EPoll (pidfd_open) and KQueue (EVFILT_PROC) selectors can only watch a specific process, so these cases now fall back to a blocking wait on a dedicated thread; joining it is fiber-scheduler aware, so the reactor keeps running.

v1.18.0

  • Fixed: Avoid entering a blocking native selector wait when an interrupt is already pending for the current thread.
Changelog

Sourced from io-event's changelog.

v1.19.3

  • Prevent URing, EPoll, and KQueue from entering a native wait when a signal exception becomes pending during the GVL transition. On Ruby versions without RB_NOGVL_PENDING_INTR_FAIL, the fallback now refreshes pending-interrupt state immediately before releasing the GVL while preserving the caller's exception-delivery timing.

v1.19.2

  • Use rb_process_status_for when available to construct URing process_wait results directly from waitid, avoiding the extra reap syscall previously needed to build a Process::Status.

v1.19.1

  • Fix Process.waitall / Process.detach under the URing selector: when io_uring's waitid reported an error (e.g. ECHILD when there are no more children), the process_wait hook raised instead of returning the error as a Process::Status, so callers that expect waitpid to report "no more children" rather than raise would fail.

v1.19.0

  • Use io_uring_prep_waitid for process_wait in the URing selector (Linux 6.7+), waiting for child exit directly in the ring instead of polling on a pidfd. The child is reaped via rb_process_status_wait (using WEXITED | WNOWAIT) to construct a correct Process::Status, and process_wait(-1, ...) / process_wait(0, ...) are now supported.
  • Support waiting for any child or a process group (pid <= 0) on all selectors. The EPoll (pidfd_open) and KQueue (EVFILT_PROC) selectors can only watch a specific process, so these cases now fall back to a blocking wait on a dedicated thread; joining it is fiber-scheduler aware, so the reactor keeps running.

v1.18.0

  • Fixed: Avoid entering a blocking native selector wait when an interrupt is already pending for the current thread.
Commits
  • b4bcf0f Bump patch version.
  • a90dcb3 Prevent native selector waits with pending signal exceptions. (#204)
  • 65967a1 Bump patch version.
  • d2faf2f Use rb_process_status_for for waitid results. (#203)
  • b39c8a1 Update rb_nogvl pending interrupt flag name. (#202)
  • e246f86 Bump patch version.
  • 3c518a3 Fix Process.waitall/detach under URing selector when no children remain. ...

@dependabot
build(deps): bump the most-gems group with 21 updates
fc026cd 
Bumps the most-gems group with 21 updates:

| Package | From | To |
| --- | --- | --- |
| [httpx](https://gitlab.com/os85/httpx) | `1.8.0` | `1.8.1` |
| [simplecov](https://github.com/simplecov-ruby/simplecov) | `0.22.0` | `1.0.2` |
| [yard](https://github.com/lsegal/yard) | `0.9.44` | `0.9.45` |
| [aws-sdk-lambda](https://github.com/aws/aws-sdk-ruby) | `1.186.0` | `1.191.0` |
| [aws-sdk-sqs](https://github.com/aws/aws-sdk-ruby) | `1.116.0` | `1.117.0` |
| [aws-sdk-cloudwatch](https://github.com/aws/aws-sdk-ruby) | `1.141.0` | `1.145.0` |
| [aws-sdk-s3](https://github.com/aws/aws-sdk-ruby) | `1.226.0` | `1.228.1` |
| [async](https://github.com/socketry/async) | `2.41.0` | `2.43.0` |
| [aws-partitions](https://github.com/aws/aws-sdk-ruby) | `1.1262.0` | `1.1273.0` |
| [aws-sdk-core](https://github.com/aws/aws-sdk-ruby) | `3.252.0` | `3.254.0` |
| [aws-sdk-kms](https://github.com/aws/aws-sdk-ruby) | `1.129.0` | `1.130.0` |
| [concurrent-ruby](https://github.com/ruby-concurrency/concurrent-ruby) | `1.3.7` | `1.3.8` |
| [console](https://github.com/socketry/console) | `1.36.0` | `1.37.0` |
| [erb](https://github.com/ruby/erb) | `6.0.4` | `6.0.6` |
| [http-2](https://github.com/igrigorik/http-2) | `1.2.0` | `1.2.1` |
| [io-event](https://github.com/socketry/io-event) | `1.17.0` | `1.19.3` |
| [json](https://github.com/ruby/json) | `2.20.0` | `2.21.1` |
| [language_server-protocol](https://github.com/mtsmfm/language_server-protocol-ruby) | `3.17.0.5` | `3.17.0.6` |
| [parser](https://github.com/whitequark/parser) | `3.3.11.1` | `3.3.12.0` |
| [rubocop-ast](https://github.com/rubocop/rubocop-ast) | `1.49.1` | `1.50.0` |
| [sass-embedded](https://github.com/sass-contrib/sass-embedded-host-ruby) | `1.101.0` | `1.102.0` |


Updates `httpx` from 1.8.0 to 1.8.1
- [Commits](https://gitlab.com/os85/httpx/compare/v1.8.0...v1.8.1)

Updates `simplecov` from 0.22.0 to 1.0.2
- [Release notes](https://github.com/simplecov-ruby/simplecov/releases)
- [Changelog](https://github.com/simplecov-ruby/simplecov/blob/main/CHANGELOG.md)
- [Commits](simplecov-ruby/simplecov@v0.22.0...v1.0.2)

Updates `yard` from 0.9.44 to 0.9.45
- [Release notes](https://github.com/lsegal/yard/releases)
- [Changelog](https://github.com/lsegal/yard/blob/main/CHANGELOG.md)
- [Commits](lsegal/yard@v0.9.44...v0.9.45)

Updates `aws-sdk-lambda` from 1.186.0 to 1.191.0
- [Release notes](https://github.com/aws/aws-sdk-ruby/releases)
- [Changelog](https://github.com/aws/aws-sdk-ruby/blob/version-3/gems/aws-sdk-lambda/CHANGELOG.md)
- [Commits](https://github.com/aws/aws-sdk-ruby/commits)

Updates `aws-sdk-sqs` from 1.116.0 to 1.117.0
- [Release notes](https://github.com/aws/aws-sdk-ruby/releases)
- [Changelog](https://github.com/aws/aws-sdk-ruby/blob/version-3/gems/aws-sdk-sqs/CHANGELOG.md)
- [Commits](https://github.com/aws/aws-sdk-ruby/commits)

Updates `aws-sdk-cloudwatch` from 1.141.0 to 1.145.0
- [Release notes](https://github.com/aws/aws-sdk-ruby/releases)
- [Changelog](https://github.com/aws/aws-sdk-ruby/blob/version-3/gems/aws-sdk-cloudwatch/CHANGELOG.md)
- [Commits](https://github.com/aws/aws-sdk-ruby/commits)

Updates `aws-sdk-s3` from 1.226.0 to 1.228.1
- [Release notes](https://github.com/aws/aws-sdk-ruby/releases)
- [Changelog](https://github.com/aws/aws-sdk-ruby/blob/version-3/gems/aws-sdk-s3/CHANGELOG.md)
- [Commits](https://github.com/aws/aws-sdk-ruby/commits)

Updates `async` from 2.41.0 to 2.43.0
- [Release notes](https://github.com/socketry/async/releases)
- [Changelog](https://github.com/socketry/async/blob/main/releases.md)
- [Commits](socketry/async@v2.41.0...v2.43.0)

Updates `aws-partitions` from 1.1262.0 to 1.1273.0
- [Release notes](https://github.com/aws/aws-sdk-ruby/releases)
- [Changelog](https://github.com/aws/aws-sdk-ruby/blob/version-3/gems/aws-partitions/CHANGELOG.md)
- [Commits](https://github.com/aws/aws-sdk-ruby/commits)

Updates `aws-sdk-core` from 3.252.0 to 3.254.0
- [Release notes](https://github.com/aws/aws-sdk-ruby/releases)
- [Changelog](https://github.com/aws/aws-sdk-ruby/blob/version-3/gems/aws-sdk-core/CHANGELOG.md)
- [Commits](https://github.com/aws/aws-sdk-ruby/commits)

Updates `aws-sdk-kms` from 1.129.0 to 1.130.0
- [Release notes](https://github.com/aws/aws-sdk-ruby/releases)
- [Changelog](https://github.com/aws/aws-sdk-ruby/blob/version-3/gems/aws-sdk-kms/CHANGELOG.md)
- [Commits](https://github.com/aws/aws-sdk-ruby/commits)

Updates `concurrent-ruby` from 1.3.7 to 1.3.8
- [Release notes](https://github.com/ruby-concurrency/concurrent-ruby/releases)
- [Changelog](https://github.com/ruby-concurrency/concurrent-ruby/blob/master/CHANGELOG.md)
- [Commits](ruby-concurrency/concurrent-ruby@v1.3.7...v1.3.8)

Updates `console` from 1.36.0 to 1.37.0
- [Release notes](https://github.com/socketry/console/releases)
- [Changelog](https://github.com/socketry/console/blob/main/releases.md)
- [Commits](socketry/console@v1.36.0...v1.37.0)

Updates `erb` from 6.0.4 to 6.0.6
- [Release notes](https://github.com/ruby/erb/releases)
- [Changelog](https://github.com/ruby/erb/blob/master/NEWS.md)
- [Commits](ruby/erb@v6.0.4...v6.0.6)

Updates `http-2` from 1.2.0 to 1.2.1
- [Release notes](https://github.com/igrigorik/http-2/releases)
- [Changelog](https://github.com/igrigorik/http-2/blob/main/CHANGELOG.md)
- [Commits](igrigorik/http-2@v1.2.0...v1.2.1)

Updates `io-event` from 1.17.0 to 1.19.3
- [Release notes](https://github.com/socketry/io-event/releases)
- [Changelog](https://github.com/socketry/io-event/blob/main/releases.md)
- [Commits](socketry/io-event@v1.17.0...v1.19.3)

Updates `json` from 2.20.0 to 2.21.1
- [Release notes](https://github.com/ruby/json/releases)
- [Changelog](https://github.com/ruby/json/blob/master/CHANGES.md)
- [Commits](ruby/json@v2.20.0...v2.21.1)

Updates `language_server-protocol` from 3.17.0.5 to 3.17.0.6
- [Changelog](https://github.com/mtsmfm/language_server-protocol-ruby/blob/main/CHANGELOG.md)
- [Commits](mtsmfm/language_server-protocol-ruby@v3.17.0.5...v3.17.0.6)

Updates `parser` from 3.3.11.1 to 3.3.12.0
- [Changelog](https://github.com/whitequark/parser/blob/master/CHANGELOG.md)
- [Commits](whitequark/parser@v3.3.11.1...v3.3.12.0)

Updates `rubocop-ast` from 1.49.1 to 1.50.0
- [Release notes](https://github.com/rubocop/rubocop-ast/releases)
- [Changelog](https://github.com/rubocop/rubocop-ast/blob/master/CHANGELOG.md)
- [Commits](rubocop/rubocop-ast@v1.49.1...v1.50.0)

Updates `sass-embedded` from 1.101.0 to 1.102.0
- [Commits](sass-contrib/sass-embedded-host-ruby@v1.101.0...v1.102.0)

---
updated-dependencies:
- dependency-name: httpx
  dependency-version: 1.8.1
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: most-gems
- dependency-name: simplecov
  dependency-version: 1.0.2
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: most-gems
- dependency-name: yard
  dependency-version: 0.9.45
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: most-gems
- dependency-name: aws-sdk-lambda
  dependency-version: 1.191.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: most-gems
- dependency-name: aws-sdk-sqs
  dependency-version: 1.117.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: most-gems
- dependency-name: aws-sdk-cloudwatch
  dependency-version: 1.145.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: most-gems
- dependency-name: aws-sdk-s3
  dependency-version: 1.228.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: most-gems
- dependency-name: async
  dependency-version: 2.43.0
  dependency-type: indirect
  update-type: version-update:semver-minor
  dependency-group: most-gems
- dependency-name: aws-partitions
  dependency-version: 1.1273.0
  dependency-type: indirect
  update-type: version-update:semver-minor
  dependency-group: most-gems
- dependency-name: aws-sdk-core
  dependency-version: 3.254.0
  dependency-type: indirect
  update-type: version-update:semver-minor
  dependency-group: most-gems
- dependency-name: aws-sdk-kms
  dependency-version: 1.130.0
  dependency-type: indirect
  update-type: version-update:semver-minor
  dependency-group: most-gems
- dependency-name: concurrent-ruby
  dependency-version: 1.3.8
  dependency-type: indirect
  update-type: version-update:semver-patch
  dependency-group: most-gems
- dependency-name: console
  dependency-version: 1.37.0
  dependency-type: indirect
  update-type: version-update:semver-minor
  dependency-group: most-gems
- dependency-name: erb
  dependency-version: 6.0.6
  dependency-type: indirect
  update-type: version-update:semver-patch
  dependency-group: most-gems
- dependency-name: http-2
  dependency-version: 1.2.1
  dependency-type: indirect
  update-type: version-update:semver-patch
  dependency-group: most-gems
- dependency-name: io-event
  dependency-version: 1.19.3
  dependency-type: indirect
  update-type: version-update:semver-minor
  dependency-group: most-gems
- dependency-name: json
  dependency-version: 2.21.1
  dependency-type: indirect
  update-type: version-update:semver-minor
  dependency-group: most-gems
- dependency-name: language_server-protocol
  dependency-version: 3.17.0.6
  dependency-type: indirect
  update-type: version-update:semver-patch
  dependency-group: most-gems
- dependency-name: parser
  dependency-version: 3.3.12.0
  dependency-type: indirect
  update-type: version-update:semver-patch
  dependency-group: most-gems
- dependency-name: rubocop-ast
  dependency-version: 1.50.0
  dependency-type: indirect
  update-type: version-update:semver-minor
  dependency-group: most-gems
- dependency-name: sass-embedded
  dependency-version: 1.102.0
  dependency-type: indirect
  update-type: version-update:semver-minor
  dependency-group: most-gems
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file ruby Pull requests that update Ruby code labels Aug 1, 2026
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Aug 1, 2026
@dependabot
dependabot Bot requested a review from rossroberts-toast as a code owner August 1, 2026 22:40
@dependabot dependabot Bot added the ruby Pull requests that update Ruby code label Aug 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@BrianSigafoos-SQ BrianSigafoos-SQ Awaiting requested review from BrianSigafoos-SQ BrianSigafoos-SQ is a code owner
@bsorbo bsorbo Awaiting requested review from bsorbo bsorbo is a code owner
@jwils jwils Awaiting requested review from jwils jwils is a code owner
@jwondrusch jwondrusch Awaiting requested review from jwondrusch jwondrusch is a code owner
@myronmarston myronmarston Awaiting requested review from myronmarston myronmarston is a code owner
@marcdaniels-toast marcdaniels-toast Awaiting requested review from marcdaniels-toast marcdaniels-toast is a code owner
@ellisandrews-toast ellisandrews-toast Awaiting requested review from ellisandrews-toast ellisandrews-toast is a code owner
@rossroberts-toast rossroberts-toast Awaiting requested review from rossroberts-toast rossroberts-toast is a code owner

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file ruby Pull requests that update Ruby code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants