Skip to content

Bump the minor-and-patch group across 1 directory with 10 updates - #2777

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/bundler/minor-and-patch-3b8ace6f35
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/bundler/minor-and-patch-3b8ace6f35

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 16, 2026

Copy link
Copy Markdown
Contributor

Bumps the minor-and-patch group with 10 updates in the / directory:

Package From To
minitest 6.0.6 6.1.0
irb 1.18.0 1.19.0
dalli 5.2.2 5.3.2
graphql 2.6.12 2.6.15
shopify-money 4.1.1 4.2.0
nokogiri 1.19.4 1.19.7
sorbet-static 0.6.13591 0.6.13680
rubydex 0.4.2 0.4.4
sorbet-static-and-runtime 0.6.13591 0.6.13680
spoom 1.8.12 1.8.13

Updates minitest from 6.0.6 to 6.1.0

Changelog

Sourced from minitest's changelog.

=== 6.1.0 / 2026-11-06

  • 1 minor enhancement:

    • Added Minitest::Test.abstract_test_case! from sexp_processor tests.
  • 9 bug fixes:

    • Added AI policy (=NO!) to README.rdoc.
    • Added Minitest.installed_at_exit? to make it easier for plugins to tell if autorun has been invoked. (sferik)
    • Added validation to -W category arg processing. (teoljungberg)
    • Allow prism 2.0 (earlopain)
    • Clarified in doco that runnable_methods & methods_matching are for public methods only. (koi1)
    • FINALLY got 100% doco coverage after fighting rdoc for YEARS!
    • Fixed RegexpError for class/method names with regex metacharacters (splattael)
    • PathExpander / Sprint: fix loading of absolute paths. (teoljungberg)
    • Removed ruby2_keywords delegation workaround from Spec. (teoljungberg)
Commits
  • 224245d prepped for release
  • 4f8b722 - Fixed RegexpError for class/method names with regex metacharacters (splattael)
  • 19badb6 Only activate coverage plugin if COV=1
  • d1353f4 Updated ruby versions/EOL dates in README
  • bd26321 - Allow prism 2.0 (earlopain)
  • 581e7d5 - Added validation to -W category arg processing. (teoljungberg)
  • 8882c77 - Added Minitest.installed_at_exit? to make it easier for plugins to tell if ...
  • 59052af - Clarified in doco that runnable_methods & methods_matching are for public m...
  • a041282 - Added AI policy (=NO!) to README.rdoc.
  • 093f803 More doco fixes / normalization
  • Additional commits viewable in compare view

Updates irb from 1.18.0 to 1.19.0

Release notes

Sourced from irb's releases.

v1.19.0

What's Changed

✨ Enhancements

🐛 Bug Fixes

📚 Documentation

🛠 Other Changes

New Contributors

Full Changelog: ruby/irb@v1.18.0...v1.19.0

Commits

Updates dalli from 5.2.2 to 5.3.2

Release notes

Sourced from dalli's releases.

v5.3.2

Bug fixes:

  • A signal arriving while Dalli::Compressor or Dalli::GzipCompressorruby/zlib#49Zlib::BufError or Zlib::DataError, or stored a truncated value that later failed to decompress. Both compressors now keep finishing the stream until zlib reports its end. GzipCompressor no longer goes through GzipWriter and GzipReader, so it now always returns decompressed values as binary strings, as Compressor does (#1299)

v5.3.1

Bug fixes:

  • Rack::Session::Dalli's 401 for a session deleted mid-request called Hash#slice on the session options. A Rails session store puts an ActionDispatch::Request::Session::Options there, so the 401 raised NoMethodError instead of expiring the cookie (#1291, @​seballot)

v5.3.0

New features:

  • enforce_read_timeout: true makes JRuby and TruffleRuby give up waiting for a reply after socket_timeout, as CRuby does. Without it, a server that accepted a request but never replied blocked the caller indefinitely on those engines, including in get and get_multi. A server that stops partway through a reply can still block. It's off by default because it costs about 8% of single-key throughput on TruffleRuby and 20-29% on JRuby, and it has no effect on CRuby or TLS connections

Bug fixes:

  • A vivify_ttl (or fetch_with_lock's lock_ttl) over 30 days now protects against a thundering herd. memcached reads a TTL over 30 days as a Unix timestamp, so the stub for a miss expired at once and every caller won the recache race. vivify_ttl is now converted like other TTLs
  • set_cas, replace_cas and delete_cas dropped a CAS that couldn't be parsed, such as 'abc', and sent an unconditional write, so the value was overwritten or deleted whatever its CAS. They now raise ArgumentError
  • flush('abc') flushed immediately. It now raises ArgumentError
  • A TTL String that isn't a whole number, such as 'abc', became 0, which means no expiry. It now raises ArgumentError, including for expires_in when the client is created
  • A TTL, CAS, incr/decr amount or initial value outside the range memcached accepts got a CLIENT_ERROR reply, which a quiet block or set_multi discarded, so the write silently did nothing. These now raise ArgumentError
  • An invalid vivify_ttl or recache_ttl raised from deep in the request and closed the connection
  • tombstone_ttl read a String with a leading zero as octal ('010' was 8) and accepted hex such as '0x10'. It's now parsed in base 10 like every other TTL, and Float::NAN raises ArgumentError rather than FloatDomainError
  • Multi-gets now raise Dalli::UnmarshalError for a value that can't be deserialized, as get does, and only after reading the rest of the replies
    • get_multi and get_multi_cas raised partway through reading a server's replies, closing the connection, and get_multi_with_metadata on more than one server silently dropped every key on that server. A large get_multi could also drop that server's keys without raising when it read the bad value while still sending requests (seen mostly on JRuby and TruffleRuby)
    • In block form the other values are still yielded, and the connections stay open. get and the other single-key reads also keep the connection open after this error now
  • get_multi, get_multi_cas and get_multi_with_metadata now return each value under the key the caller passed. They rebuilt the key from the one memcached returned, so:
    • With a namespace, a key that isn't valid UTF-8 (such as "\xff".b) raised ArgumentError for the whole call
    • A key too long to send as is (over 250 bytes, or once base64-encoded) came back under its digested form
    • A binary key with non-ASCII bytes came back tagged UTF-8, so result.key?(key) was false
    • A key given more than once is now requested once, and a block is yielded it once
  • On TruffleRuby, a process spawned while Dalli had a connection open (with system, spawn or backticks) inherited the socket and kept the connection open on memcached's side until it exited. Dalli's sockets are now close-on-exec, as CRuby makes them by default
  • A request that failed after it was sent, such as one whose reply timed out, was sent again even though memcached may have applied it. incr, decr, append and prepend could be applied twice, and add and writes with a CAS could report failure for a write that had succeeded. Once some of a request has been sent, Dalli now retries only requests that are safe to apply twice (see Other changes)
  • When a server stopped while connected, the multi-key operations (get_multi, get_multi_cas, get_multi_with_metadata, set_multi and delete_multi) returned its keys as misses, or left them unwritten, instead of raising Dalli::NetworkError as documented. The retry found the server down and skipped it as if it had been down from the start. Without failover they now raise. With failover the keys still go to another server, as they do for get and set, when the retry can't connect to the failed server. A server that accepts the retry's connection and fails again is marked down during the operation, which raises Dalli::NetworkError either way (#1263, @​jaideeppyne)
  • Rack::Session::Dalli: a stored session that couldn't be decoded (for example after changing the serializer, or removing a class that sessions stored) left the user on a session that was never saved, with no new cookie, so they couldn't log in until the cookie was cleared or the session expired. It's now treated as missing: the request gets a new session and cookie, and a warning is logged
  • A reply value is now checked for the CRLF that should follow it. Values were read by their declared size alone, so a size that didn't match the value (a broken proxy, or an injected reply) was returned as a hit with a nil value, or the rest of the value was read as the next reply. These now raise Dalli::DalliError and close the connection, as a value size out of range does
  • get_multi_cas, and get_multi on more than one server, returned a server's keys as misses when it sent nothing within socket_timeout, without retrying or counting a failure. They now treat it like any read timeout: the batch is retried, and Dalli::NetworkError is raised once the server is marked down, as get, get_multi_with_metadata and single-server get_multi already did. socket_timeout also used to cover the whole batch, so a large reply that was still arriving could be cut off, with its remaining keys returned as misses. The wait now starts again whenever data arrives (#1285)
  • A reply key marked base64 that isn't valid base64 raised ArgumentError from get_multi, get_multi_cas and get_multi_with_metadata, which callers rescuing Dalli::DalliError didn't catch. It now raises Dalli::DalliError. Found by the new fuzz targets
  • set_multi and delete_multi on more than one server retried forever, hanging the caller, when a server accepted their writes and then closed the connection before replying. Each quiet write reset the server's failure count, so it never reached socket_max_failures. Only a request whose reply is read resets it now, and the server is marked down and Dalli::NetworkError raised, as for get
  • Since 5.2.0, on JRuby with TLS, Dalli could wait socket_timeout for part of a reply that had already arrived, because jruby-openssl can hold it where neither IO.select nor OpenSSL's pending reports it. With the multi-get change above (#1285), that wait would have made get_multi raise Dalli::NetworkError. Dalli now reads on JRuby until the TLS socket would block

Other changes:

  • Rack::Session::Dalli docs: without expire_after, sessions are stored with no expiry and stay in memcached until deleted or evicted
  • Numeric arguments are checked before anything is written, so a bad one raises ArgumentError without affecting the connection or earlier writes in a quiet block. Integers and Strings of decimal digits (such as '300') are accepted throughout
    • A TTL (ttl, expires_in, vivify_ttl, lock_ttl, tombstone_ttl) must fit memcached's signed 32-bit expiration time once a TTL over 30 days is converted to a Unix time. A negative TTL is still accepted and expires the item. A Float or ActiveSupport::Duration TTL is still converted with to_i
    • A CAS, an incr/decr amount or initial value, and a flush delay must be from 0 to 2**64 - 1. A Float now raises; incr(key, 0.9) used to truncate the amount to 0. A String amount such as '5' now works
    • fetch, fetch_with_lock, cas and cas! check ttl before running the block, so a bad one raises before any side effects. fetch checks it on a hit too
    • Dalli::Protocol::TtlSanitizer.sanitize raises ArgumentError for a String that isn't a whole number instead of returning 0

... (truncated)

Changelog

Sourced from dalli's changelog.

5.3.2

Bug fixes:

  • A signal arriving while Dalli::Compressor or Dalli::GzipCompressorruby/zlib#49Zlib::BufError or Zlib::DataError, or stored a truncated value that later failed to decompress. Both compressors now keep finishing the stream until zlib reports its end. GzipCompressor no longer goes through GzipWriter and GzipReader, so it now always returns decompressed values as binary strings, as Compressor does (#1299)

5.3.1

Bug fixes:

  • Rack::Session::Dalli's 401 for a session deleted mid-request called Hash#slice on the session options. A Rails session store puts an ActionDispatch::Request::Session::Options there, so the 401 raised NoMethodError instead of expiring the cookie (#1291, @​seballot)

5.3.0

New features:

  • enforce_read_timeout: true makes JRuby and TruffleRuby give up waiting for a reply after socket_timeout, as CRuby does. Without it, a server that accepted a request but never replied blocked the caller indefinitely on those engines, including in get and get_multi. A server that stops partway through a reply can still block. It's off by default because it costs about 8% of single-key throughput on TruffleRuby and 20-29% on JRuby, and it has no effect on CRuby or TLS connections

Bug fixes:

  • A vivify_ttl (or fetch_with_lock's lock_ttl) over 30 days now protects against a thundering herd. memcached reads a TTL over 30 days as a Unix timestamp, so the stub for a miss expired at once and every caller won the recache race. vivify_ttl is now converted like other TTLs
  • set_cas, replace_cas and delete_cas dropped a CAS that couldn't be parsed, such as 'abc', and sent an unconditional write, so the value was overwritten or deleted whatever its CAS. They now raise ArgumentError
  • flush('abc') flushed immediately. It now raises ArgumentError
  • A TTL String that isn't a whole number, such as 'abc', became 0, which means no expiry. It now raises ArgumentError, including for expires_in when the client is created
  • A TTL, CAS, incr/decr amount or initial value outside the range memcached accepts got a CLIENT_ERROR reply, which a quiet block or set_multi discarded, so the write silently did nothing. These now raise ArgumentError
  • An invalid vivify_ttl or recache_ttl raised from deep in the request and closed the connection
  • tombstone_ttl read a String with a leading zero as octal ('010' was 8) and accepted hex such as '0x10'. It's now parsed in base 10 like every other TTL, and Float::NAN raises ArgumentError rather than FloatDomainError
  • Multi-gets now raise Dalli::UnmarshalError for a value that can't be deserialized, as get does, and only after reading the rest of the replies
    • get_multi and get_multi_cas raised partway through reading a server's replies, closing the connection, and get_multi_with_metadata on more than one server silently dropped every key on that server. A large get_multi could also drop that server's keys without raising when it read the bad value while still sending requests (seen mostly on JRuby and TruffleRuby)
    • In block form the other values are still yielded, and the connections stay open. get and the other single-key reads also keep the connection open after this error now
  • get_multi, get_multi_cas and get_multi_with_metadata now return each value under the key the caller passed. They rebuilt the key from the one memcached returned, so:
    • With a namespace, a key that isn't valid UTF-8 (such as "\xff".b) raised ArgumentError for the whole call
    • A key too long to send as is (over 250 bytes, or once base64-encoded) came back under its digested form
    • A binary key with non-ASCII bytes came back tagged UTF-8, so result.key?(key) was false
    • A key given more than once is now requested once, and a block is yielded it once
  • On TruffleRuby, a process spawned while Dalli had a connection open (with system, spawn or backticks) inherited the socket and kept the connection open on memcached's side until it exited. Dalli's sockets are now close-on-exec, as CRuby makes them by default
  • A request that failed after it was sent, such as one whose reply timed out, was sent again even though memcached may have applied it. incr, decr, append and prepend could be applied twice, and add and writes with a CAS could report failure for a write that had succeeded. Once some of a request has been sent, Dalli now retries only requests that are safe to apply twice (see Other changes)
  • When a server stopped while connected, the multi-key operations (get_multi, get_multi_cas, get_multi_with_metadata, set_multi and delete_multi) returned its keys as misses, or left them unwritten, instead of raising Dalli::NetworkError as documented. The retry found the server down and skipped it as if it had been down from the start. Without failover they now raise. With failover the keys still go to another server, as they do for get and set, when the retry can't connect to the failed server. A server that accepts the retry's connection and fails again is marked down during the operation, which raises Dalli::NetworkError either way (#1263, @​jaideeppyne)
  • Rack::Session::Dalli: a stored session that couldn't be decoded (for example after changing the serializer, or removing a class that sessions stored) left the user on a session that was never saved, with no new cookie, so they couldn't log in until the cookie was cleared or the session expired. It's now treated as missing: the request gets a new session and cookie, and a warning is logged
  • A reply value is now checked for the CRLF that should follow it. Values were read by their declared size alone, so a size that didn't match the value (a broken proxy, or an injected reply) was returned as a hit with a nil value, or the rest of the value was read as the next reply. These now raise Dalli::DalliError and close the connection, as a value size out of range does
  • get_multi_cas, and get_multi on more than one server, returned a server's keys as misses when it sent nothing within socket_timeout, without retrying or counting a failure. They now treat it like any read timeout: the batch is retried, and Dalli::NetworkError is raised once the server is marked down, as get, get_multi_with_metadata and single-server get_multi already did. socket_timeout also used to cover the whole batch, so a large reply that was still arriving could be cut off, with its remaining keys returned as misses. The wait now starts again whenever data arrives (#1285)
  • A reply key marked base64 that isn't valid base64 raised ArgumentError from get_multi, get_multi_cas and get_multi_with_metadata, which callers rescuing Dalli::DalliError didn't catch. It now raises Dalli::DalliError. Found by the new fuzz targets
  • set_multi and delete_multi on more than one server retried forever, hanging the caller, when a server accepted their writes and then closed the connection before replying. Each quiet write reset the server's failure count, so it never reached socket_max_failures. Only a request whose reply is read resets it now, and the server is marked down and Dalli::NetworkError raised, as for get
  • Since 5.2.0, on JRuby with TLS, Dalli could wait socket_timeout for part of a reply that had already arrived, because jruby-openssl can hold it where neither IO.select nor OpenSSL's pending reports it. With the multi-get change above (#1285), that wait would have made get_multi raise Dalli::NetworkError. Dalli now reads on JRuby until the TLS socket would block

Other changes:

... (truncated)

Commits
  • 9d8c380 Prepare 5.3.2 release (#1303)
  • cba8746 Finish zlib streams that a signal interrupts (#1300)
  • 2ef90c3 Tick the credentials and get_multi retry follow-ups in the hardening plan (#1...
  • 498c997 Prepare 5.3.1 release (#1296)
  • ec5ab3a Expire the session cookie when Rails session options are not a Hash (#1291)
  • 4bbd037 Prepare 5.3.0 release (#1292)
  • 6009faa Read JRuby TLS sockets until they would block (#1293)
  • d6bc9f5 Retry and raise when a server sends nothing to a multi-get (#1289)
  • e0e2aaf Stop set_multi and delete_multi retrying forever on a dropped connection (#1288)
  • 3cce253 Restore quiet set throughput with fast paths for valid TTLs and CAS (#1290)
  • Additional commits viewable in compare view

Updates graphql from 2.6.12 to 2.6.15

Changelog

Sourced from graphql's changelog.

2.6.15 (9 Nov 2026)

Security

This release includes security patches for the following:

New features

  • Continue Sorbet adoption #5867 #5872
  • Analysis: also support GraphQL::ExecutionError #5870

Bug fixes

  • Directives: don't drop repeated instances of repeatable directives on interfaces or on subclasses with inherited directives #5823
  • Parser: improve stack overflow error message #5857
  • Parser: reject variables in default values #5864
  • Parser: improve handling of CR line endings #5848 #5847
  • Generator: improve generated controller for @defer handling #5855
  • Parser: improve numeric lexical boudaries #5856
  • ActionCable: improve memory cleanup #5860
  • Parser: preserve newlines after escaped backslashes #5858
  • Execution::Next: remove duplicate input coercion
  • Validation: fix NoMethodError #5876
  • Validation: update callers to types #5868
  • Lexer: speedup #5880 , documentation #5883
  • Parser: fix column count with BOM #5886
  • Parser: improve token limit handling #5887
  • Execution::Next: improve rescue_from compatibility

2.6.14 (29 Oct 2026)

Security

Two patches relating to loopholes in authorization edge cases (legacy and next runtimes):

New Features

  • Schema.from_definition: speed up #5832
  • Execution::Next: improve dataloader batching in .authorized?
  • Sorbet adoption #5825 #5852

... (truncated)

Commits
  • 26346d3 2.6.15
  • 33d198f Merge commit from fork
  • e692b55 Merge commit from fork
  • 32647a5 Merge commit from fork
  • d340c94 Merge commit from fork
  • f1a95c3 Merge commit from fork
  • 79eb4f9 Merge pull request #5883 from ydah/document-lexer-match-state
  • e8d66ac Merge pull request #5890 from ydah/fix-c-parser-tokenize-helper
  • 3af037e Remove unused CParser.tokenize_with_c
  • 84cac50 Merge pull request #5891 from fuzzyrichie/fix-next-resolver-rescue-from-field
  • Additional commits viewable in compare view

Updates shopify-money from 4.1.1 to 4.2.0

Release notes

Sourced from shopify-money's releases.

v4.2.0

What's Changed

Full Changelog: Shopify/money@v4.1.1...v4.2.0

Commits
  • 32a9be9 Merge pull request #538 from Shopify/jackie/release-4.1.2
  • 0e8b24c Use minor version 4.2.0 for the release
  • d37d943 Bump shopify-money to 4.1.2
  • b415d69 Merge pull request #536 from Shopify/Vault-78027
  • a3ddac7 Merge pull request #537 from Shopify/jackie/78027-early-magnitude-check
  • a04160e Validate money magnitude before subunit arithmetic
  • 45cdb69 Reject Money values with more than 1000 integer digits
  • 4d9b012 Fix Money#clamp docs, signature, and specs
  • 23e8d18 Delegate Money#clamp to Comparable#clamp
  • b3d4cb0 Merge pull request #532 from alexcwatt/perf/plain-defs-for-delegators
  • Additional commits viewable in compare view

Updates nokogiri from 1.19.4 to 1.19.7

Release notes

Sourced from nokogiri's releases.

v1.19.7 / 2026-11-02

Fixed

  • [CRuby] Compile against Ruby 4.1.0-preview1, which defines HAVE_RB_LEN_T but not RB_FIX2LEN. (#3755) @​andrewfader
8f5e15d299602456406e1f03a9f3456cceb33a0722811e818d2ee2214eb4c84a  nokogiri-1.19.7-aarch64-linux-gnu.gem
efe0c3602e6e54521bc21c681930ce5568e2d11203de17400710b2b3ca2e4cb4  nokogiri-1.19.7-aarch64-linux-musl.gem
7fd1907125691aa89e838cc91161761c758b4e17bb32f0dd9b5515a82cc759af  nokogiri-1.19.7-arm-linux-gnu.gem
28d0ff0c87b6bb2e56580323a6fb049d5d4a02b94f0958fdd47e9ac146991c77  nokogiri-1.19.7-arm-linux-musl.gem
f27d7f25f4873fbc3aa35a2cc2fb680c98555fec1925348da439d0869d541142  nokogiri-1.19.7-arm64-darwin.gem
3c97c2874993b890386ac487c41578d173e10621d80c2063830d032839487c3b  nokogiri-1.19.7-java.gem
9ab6ea96ab479a5ff391196de73b5abf660926ea7e4c57cb1f35adf754f1d066  nokogiri-1.19.7-x64-mingw-ucrt.gem
508e81e8c5f84aaa240dce981bf1c43faae60808726f0ce7024ee92effc5cafe  nokogiri-1.19.7-x86_64-darwin.gem
25865ccb462f714e712fdf8906fde07849cb6704a808e3d629d75baa5af5dd3b  nokogiri-1.19.7-x86_64-linux-gnu.gem
464d1f3dfb0d53cf54c0c6a7e23e8e91cf68ec3cafc2b27dc4a7682f2d9bf546  nokogiri-1.19.7-x86_64-linux-musl.gem
abe94507c54cb18f872777b16bdca4aad32b1abdc4c52fe843f1c80fbdf992b8  nokogiri-1.19.7.gem

Full Changelog: sparklemotion/nokogiri@v1.19.6...v1.19.7

v1.19.6 / 2026-11-02

Fixed

  • [JRuby] Parsing or reparenting an HTML4 element that has an xmlns attribute and a child element no longer raises NullPointerException. This was a regression in v1.19.5. (#3753) @​flavorjones
746fca23be3cd3f121cabab65cb44c52049e4cf9f0d36e7e8c3c0eb6cc298c57  nokogiri-1.19.6-aarch64-linux-gnu.gem
4a5620da1c52150e0343bd2bba7dbd9b3899b5eb41687dc1942c9092d81e52a3  nokogiri-1.19.6-aarch64-linux-musl.gem
574e50ddd99ed71aaa868027d84eb3b9f051e55fe07ddc844e4fdd654be953fc  nokogiri-1.19.6-arm-linux-gnu.gem
c20ea8d8c92cbaa475f0952f755dea88cf6e3ace8b49d634a0a5385a1feaea10  nokogiri-1.19.6-arm-linux-musl.gem
0a89005ba8cf40c7bd580f4c0873f5f11e5866a99e364764fb59ac6516f560d0  nokogiri-1.19.6-arm64-darwin.gem
4068744c2afb9c2596666a5b02fe633be1c58abb3bf2c9d06c962ede95c55fba  nokogiri-1.19.6-java.gem
b5768c5dab09abe39e6e1329f692db191688398964f7d2c18caaa19aa00f5421  nokogiri-1.19.6-x64-mingw-ucrt.gem
8f15f820fa1373d8685ae48cdd8020d923b4104db74d149d1235ddae956469a6  nokogiri-1.19.6-x86_64-darwin.gem
ad1e228c3bc873e4f4fc4f845d7e37b4d3648af537acd7b5e8463cce5693065b  nokogiri-1.19.6-x86_64-linux-gnu.gem
c92b29e897f4ddc19bea67188695aab667f695e74592a5c8741642ecb25d34d9  nokogiri-1.19.6-x86_64-linux-musl.gem
a61e7192fc2691c23bc0241907c4dbcb70ada6ab904796ce2426a57171022c8f  nokogiri-1.19.6.gem
</tr></table> 

... (truncated)

Changelog

Sourced from nokogiri's changelog.

v1.19.7 / 2026-11-02

Fixed

  • [CRuby] Compile against Ruby 4.1.0-preview1, which defines HAVE_RB_LEN_T but not RB_FIX2LEN. (#3755) @​andrewfader

v1.19.6 / 2026-11-02

Fixed

  • [JRuby] Parsing or reparenting an HTML4 element that has an xmlns attribute and a child element no longer raises NullPointerException. This was a regression in v1.19.5. (#3753) @​flavorjones

v1.19.5 / 2026-11-01

Security

  • [CRuby] (Low) Fixed a possible use-after-free when an attribute value is replaced via Node#[]= or Node#lang= while Ruby objects still reference the attribute's children. See GHSA-3w22-6jfg-527w for more information.
  • [CRuby] (Low) The HTML5 serializer now escapes text inside noscript unless the document was parsed with parse_noscript_content_as_text: true, preventing a mutation XSS in applications that allow noscript in sanitized HTML. A fragment now parses noscript content the same way as its document, and raises ArgumentError if given a conflicting parse_noscript_content_as_text: value. Comments and raw-text elements inside noscript are still serialized unchanged, as the HTML standard requires, so applications that sanitize HTML and allow noscript should parse with parse_noscript_content_as_text: true or remove noscript elements. See GHSA-4p39-36wj-23h4 for more information.
  • [JRuby] (Low) NONET now blocks external DTDs and entities whose systemId uses a short-form IPv4 host such as 127.1, or is an absolute path in a document parsed from a network URL. Previously Nokogiri fetched them over the network during a parse with DTDLOAD or NOENT, potentially enabling SSRF. See GHSA-v995-44v6-5fqm for more information.

Improved

  • [CRuby] The HTML5 parser now has linear performance when parsing many attributes. Previously performance was quadratic due to two hotspots, one in detecting duplicate attributes and one in constructing the libxml2 data structures. (#3393) @​flavorjones
  • [CRuby] Improved XPath argument marshalling performance by using ALLOCV_N instead of rb_gc_register_address. (#3648) @​jhawthorn

Fixed

  • Node#namespace= now declares the namespace on the node when no declaration of its prefix is in scope there. Previously, on CRuby, a node given a namespace and then moved under an element that binds the same prefix, or the default namespace, to a different URI was serialized in that other namespace. On JRuby, the namespace was missing from Node#namespace_definitions. (#3459, #3462) @​flavorjones
  • XML::Reader is no longer affected by changes made to its source String after the reader is created. Previously, such a change could make the reader parse the changed String on JRuby, or changed or freed memory on CRuby with libxml2 < 2.11. (#3694) @​flavorjones
  • Node#namespace = false now raises TypeError. Previously it crashed the process on CRuby and raised ClassCastException on JRuby. (#3719) @​flavorjones
  • XML::XPathContext.new and XML::XPathContext#node= raise TypeError when the argument is not a Node. Previously, on CRuby, most such arguments crashed the process. (#3720) @​flavorjones
  • CSS an+b selectors with a zero or negative step now follow the Selectors spec: :nth-child(0n+3) matches only the third element (previously nothing), 0n-1 matches nothing instead of raising ZeroDivisionError, and -n+0 / -2n match nothing instead of every (or every other) element. @​afurm
  • CSS #id, .class and attribute selectors whose value contains a quote character, such as #it\'s or [a=\'b\'], now match that value. Previously they raised Nokogiri::XML::XPath::SyntaxError or generated an XPath query with a different meaning. An #id selector containing an escaped newline no longer drops the text after it. (#3724, #3727) @​flavorjones
  • CSS :contains() arguments, custom pseudo-class string arguments, and element names containing a CSS escape, such as p:contains('it\'s') or a\-b, now match. Previously they raised Nokogiri::XML::XPath::SyntaxError. An element name that is not an XML name after unescaping, such as a\!b, raises Nokogiri::CSS::SyntaxError, except as an unprefixed name in an HTML5 document, where it matches by local name. In ids, classes, attribute values, element names and string arguments, an escape for U+0000, a surrogate, or a code point above U+10FFFF now decodes to U+FFFD, and a vertical tab after a hexadecimal escape is no longer dropped, as CSS Syntax Level 3 requires. (#3728, #3729) @​flavorjones
  • CSS attribute names containing a CSS escape, such as [a\-b], now match. Previously they raised Nokogiri::XML::XPath::SyntaxError. An unprefixed attribute name that cannot be written as an XPath name test after unescaping, such as [\@click] or [\:class], matches an attribute with that exact name in no namespace. The HTML parsers create such attributes. A prefixed one, such as [x|a\!b], raises Nokogiri::CSS::SyntaxError. (#3732, #3735) @​flavorjones
  • [CRuby] The HTML5 serializer escapes < and > in attribute values as &lt; and &gt;, following whatwg/html#6362. Previously they were written literally. (#3529, #3741) @​flavorjones
  • [CRuby] Reparenting removes a node's declaration of a prefix that the new parent binds to the same URI. (#3462) @​flavorjones
  • [CRuby] Builder now correctly builds namespaced nodes that define their own namespace when that ns prefix collides with one defined by the parent (or another ancestor). (#3458, #3461) @​flavorjones
  • [CRuby] Reader.outer_xml and .inner_xml properly capture syntax errors. (#3558) @​flavorjones
  • [CRuby] XML::SAX::PushParser and HTML4::SAX::PushParser keep parsing correctly after GC compaction relocates their SAX parser. (#3665) @​zanker
  • [CRuby] XML::Reader keeps reading correctly when GC compaction runs. Previously, compaction could move the IO or String the reader was created from, and the reader then crashed or parsed the wrong bytes. (#3666, #3668) @​zanker
  • [CRuby] XSLT::Stylesheet#transform calls custom XSLT extension functions correctly when GC compaction runs. Previously, after compaction moved a stylesheet that uses an extension module, a later transform raised an exception or crashed. (#3667) @​jeremy
  • [CRuby] XSLT::Stylesheet#transform passes the correct params when GC compaction runs while it converts a param with #to_str. Previously, compaction could move the bytes of earlier short params, and the transform raised RuntimeError or silently left a param empty. (#3670) @​flavorjones
  • [CRuby] XML::SAX::ParserContext.io and HTML4::SAX::ParserContext.io keep parsing correctly after GC compaction relocates the IO. (#3669) @​zanker
  • [CRuby] Document#canonicalize passes the correct inclusive namespace prefixes when it converts a prefix with #to_str, and when GC compaction runs during canonicalization. Previously, libxml2 could read freed or moved memory, and the output lost namespaces or Ruby crashed. Raising on a prefix with a null byte also no longer leaks memory. (#3714, #3750) @​Priyank-gouda678 @​flavorjones
  • [CRuby] XSLT::Stylesheet#transform calls custom XSLT extension functions correctly when GC compaction runs during the transform. Previously, compaction could move an extension handler instance, and a later call to one of its functions raised an exception or crashed. (#3748) @​flavorjones

... (truncated)

Commits
  • cb8cd03 version bump to v1.19.7
  • 51ffdd7 Merge pull request #3756 from sparklemotion/card-940-rb-fix2len-preview1-v1-19-x
  • 0ad11d1 doc: say Ruby 4.1.0-preview1 lacks only RB_FIX2LEN
  • d884dcf Define RB_NUM2LEN and RB_FIX2LEN independently of HAVE_RB_LEN_T

Bumps the minor-and-patch group with 10 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [minitest](https://github.com/minitest/minitest) | `6.0.6` | `6.1.0` |
| [irb](https://github.com/ruby/irb) | `1.18.0` | `1.19.0` |
| [dalli](https://github.com/petergoldstein/dalli) | `5.2.2` | `5.3.2` |
| [graphql](https://github.com/rmosolgo/graphql-ruby) | `2.6.12` | `2.6.15` |
| [shopify-money](https://github.com/Shopify/money) | `4.1.1` | `4.2.0` |
| [nokogiri](https://github.com/sparklemotion/nokogiri) | `1.19.4` | `1.19.7` |
| [sorbet-static](https://github.com/sorbet/sorbet) | `0.6.13591` | `0.6.13680` |
| [rubydex](https://github.com/Shopify/rubydex) | `0.4.2` | `0.4.4` |
| [sorbet-static-and-runtime](https://github.com/sorbet/sorbet) | `0.6.13591` | `0.6.13680` |
| [spoom](https://github.com/Shopify/spoom) | `1.8.12` | `1.8.13` |



Updates `minitest` from 6.0.6 to 6.1.0
- [Changelog](https://github.com/minitest/minitest/blob/master/History.rdoc)
- [Commits](minitest/minitest@v6.0.6...v6.1.0)

Updates `irb` from 1.18.0 to 1.19.0
- [Release notes](https://github.com/ruby/irb/releases)
- [Commits](ruby/irb@v1.18.0...v1.19.0)

Updates `dalli` from 5.2.2 to 5.3.2
- [Release notes](https://github.com/petergoldstein/dalli/releases)
- [Changelog](https://github.com/petergoldstein/dalli/blob/main/CHANGELOG.md)
- [Commits](petergoldstein/dalli@v5.2.2...v5.3.2)

Updates `graphql` from 2.6.12 to 2.6.15
- [Release notes](https://github.com/rmosolgo/graphql-ruby/releases)
- [Changelog](https://github.com/rmosolgo/graphql-ruby/blob/master/CHANGELOG.md)
- [Commits](rmosolgo/graphql-ruby@v2.6.12...v2.6.15)

Updates `shopify-money` from 4.1.1 to 4.2.0
- [Release notes](https://github.com/Shopify/money/releases)
- [Commits](Shopify/money@v4.1.1...v4.2.0)

Updates `nokogiri` from 1.19.4 to 1.19.7
- [Release notes](https://github.com/sparklemotion/nokogiri/releases)
- [Changelog](https://github.com/sparklemotion/nokogiri/blob/main/CHANGELOG.md)
- [Commits](sparklemotion/nokogiri@v1.19.4...v1.19.7)

Updates `sorbet-static` from 0.6.13591 to 0.6.13680
- [Release notes](https://github.com/sorbet/sorbet/releases)
- [Commits](https://github.com/sorbet/sorbet/commits)

Updates `rubydex` from 0.4.2 to 0.4.4
- [Release notes](https://github.com/Shopify/rubydex/releases)
- [Commits](Shopify/rubydex@v0.4.2...v0.4.4)

Updates `sorbet-static-and-runtime` from 0.6.13591 to 0.6.13680
- [Release notes](https://github.com/sorbet/sorbet/releases)
- [Commits](https://github.com/sorbet/sorbet/commits)

Updates `spoom` from 1.8.12 to 1.8.13
- [Release notes](https://github.com/Shopify/spoom/releases)
- [Commits](Shopify/spoom@v1.8.12...v1.8.13)

---
updated-dependencies:
- dependency-name: minitest
  dependency-version: 6.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: irb
  dependency-version: 1.19.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: dalli
  dependency-version: 5.3.2
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: graphql
  dependency-version: 2.6.15
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: shopify-money
  dependency-version: 4.2.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: nokogiri
  dependency-version: 1.19.7
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: sorbet-static
  dependency-version: 0.6.13680
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: rubydex
  dependency-version: 0.4.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: sorbet-static-and-runtime
  dependency-version: 0.6.13680
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: spoom
  dependency-version: 1.8.13
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot requested a review from a team as a code owner November 16, 2026 21:45
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file ruby Pull requests that update Ruby code labels Nov 16, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants