- ruby-talk - ml.ruby-lang.org

[ruby-talk:444862] [ANN] httpx 1.9.0 released
by Tiago Cardoso 14 Oct '26

14 Oct '26

httpx 1.8.0 has been released. ``` HTTPX.get("https://gitlab.com/honeyryderchuck/httpx <https://gitlab.com/honeyryderchuck/httpx>") ``` HTTPX is an HTTP client library for the Ruby programming language. Among its features, it supports: * HTTP/2 and HTTP/1.x protocol versions * Concurrent requests by default * Simple and chainable API * Proxy Support (HTTP(S), CONNECT tunnel, Socks4/4a/5) * Simple Timeout System * Lightweight by default (require what you need) And also: * Compression (gzip, deflate, brotli) * Streaming Requests * Authentication (Basic Auth, Digest Auth, AWS Sigv4) * Expect 100-continue * Multipart Requests * Cookies * HTTP/2 Server Push * H2C Upgrade * Automatic follow redirects * International Domain Names * GRPC * Circuit breaker * WebDAV * SSRF Filter * Response caching * HTTP/2 bidirectional streaming * QUERY HTTP verb * Server Sent Events * Tracing * Request Hedging * Datadog integration * Faraday integration * Webmock integration * Sentry integration Here are the updates since the last release: # 1.9.0 ## Features ### `:hedging` plugin The `:hedging` plugin implements a strategy called "request hedging", whereby a request is sent two times, over different connections, and picking up whichever arrives first. ```ruby http = HTTP.plugin(:hedging) http.get("http://www.example.com") # sent two times, only the fastest one comes back... ``` You can read more about it in https://gitlab.com/os85/httpx/wikis/Hedging . ### `:proxy/http` plugin: new options `:proxy_headers` and `:enable_proxy_tunnel` The `:proxy/http` plugin (which gets automatically loaded by the `:proxy` plugin) gains two new options. #### `:proxy_headers` Can be passed a separate set of HTTP headers, which are going to be sent to the proxy when establishing the CONNECT proxy tunnel. ```ruby http = HTTPX.plugin(:proxy).with(proxy_headers: { "x-proxy-1" => "foo" }, headers: { "x-header-1" => "bar" }).get("https://example.com") # -> CONNECT example.com HTTP/1.1 # -> Host: example.com # -> X-Proxy-1: foo # ... # <- 200 OK # ... # -> GET / HTTP/1.1 # -> X-Headers-1: bar # ... ``` #### `:enable_proxy_tunnel` When set to `true`, it forces the establishment of a CONNECT proxy tunnel before sending the request. Bear in mind that this will be the norm for `https://` requests, so only use this in cases where the requests are to be sent to an `http://` URL and a CONNECT proxy tunnel is required. ## Improvements * `:request_timeout` will also observe the connect phase, in case a request is sent to an idle connection. This means that, if you're using `:request_timeout`, you no longer need to specify `:connect_timeout`. * The same will happen if you're using `:total_request_timeout`. * do not require "io/wait" anymore for ruby 3.2 or higher. * `:proxy/http` plugin: raise a `HTTPX::ConnectTimeoutError` if there was a timeout error while waiting for the CONNECT request to complete. ## Bugfixes * `:auth` plugin: fixed clause inverted check, which caused a new token to always be generated on retry. * `:auth` plugin: take auth_header_expires_at into account when deciding to regenerate on retry (token may have expired by the time the request will be retried). * `:tracing` plugin: fixed request initial time calculation in order to take into account the time to wait for a PING correctly. * `:tracing` plugin: fixed request initial time calculation for pending requests which were waiting for the connect phase and errored meanwhile. * `:proxy/http` plugin: `:headers` will not be sent anymore to the proxy when establishing the CONNECT proxy tunnel. * socket connect timeout bookkeeping is fixed, where in a multi request scenario, connect timeout errors shall not be raised too early if an error happens before the remainder of connections elapses. * `:proxy` plugin: allow proxy params to be frozen, which also fixes an issue where proxies identified as unhealthy by a previous request, would still be retried on for different hostnames. * `:callbacks` plugin: fix broken visibility of session `#close` method. * native resolver: retry dns queries on not-imp and refused errors (treats them as transient resolver errors). * `webmock` adapter: fix emission of `:response` callback so that this only happens after the body is fully buffered (which makes the `:callbacks` plugin `.on_response_completed` callback works the same way when and when not stubbed). * `:addresses`: fix support for the documented variant where a hostname/ips hash is passed. * `http2`: fix interests calculation, so that: * a connection expects to read from connections which still have in-transit streams. * an HTTP/2 with no available flow control window in its streams will wait for incoming WINDOW_UPDATE frames. * `http2`: pause buffering the request body if there's no available control window in the corresponding stream or connection. * `http2`: reset the ping timer too if a connection receives a GOAWAY frame while waiting for a PING to be ack'ed. * wait for read or write for any operation, considering that `OpenSSL::SSL::SSLSocket` objects may return both `.wait_readable` and `:wait_writable` for reads and writes. * when using `:max_requests`, also account for inflight requests when deciding to send it to the parser or the pending queue. * fixed `HTTPX::Options#merge` which was not freezing the resulting options object, something which happens when enabling plugins, which made resulting sessions unusable across Ractors. * fixed the `Alt-Svc` header parser to be able to parse values with multiple authorities. * fixed request params handling so that they are passed to all requests invoked (instead of only the first of them). ## Chore * Emit a warning message whenever the connection is deactivated with pending requests; the message contains an internal state which should help debug it. # 1.8.4 ## Improvements * send requests which were not sent, or were not processed by the server, when the server sends back a GOAWAY frame (which is deemed recoverable, like when there's no error), after forcing a reconnection (instead of bubbling up the GOAWAY error for all of them). ## Bugfixes * `:retries` plugin: also retry requests which failed due to a RST_STREAM frame with REFUSED_STREAM error code. * `:retries` plugin: resend requests which were piped to a closed connection internally. * `:proxy` plugin: fix issue related with reconnecting inactive connections shut down by the peer, when used with the `:persistent` plugin, where the CONNECT request wasn't being sent to establish the tunnel. * fixed compatibility issue starting with the `json` gem 3.0.0, when calling `HTTPX::Response#json`. * avoid bookkeeping issue in session, where the `on_response_arrived` on a request may be called more than once (which it can happen in the `:follow_redirects` plugin, where a request may have completed due to an error, while the request is waiting to be resent due to `retry-after`). # 1.8.3 ## Bugfixes * options print a warning instead of raising an error on unknown option * The approach introduced in the previous version, of erroring on something people have been accidentally relying on, is too strict in hindsight for a patch version. This was reverted, and instead, a deprecation warning will be printed, to give time for folks to migrate. * The format of option messages (exceptions and warnings) also slightly changes to wrap the option in quotes, for proper highlighting. # 1.8.2 ## Improvements * `:proxy` plugin: allow setting `:no_proxy` option to `"*"` (or `["*"]`) to allow bypassing proxy for all requests. * Extending sessions with unknown options will now raise an error, instead of silently ignoring them (consistent with the initialization case now): ```ruby session = HTTPX.with(unknown_option: 1) # will raise a HTTPX::Error: unknown option: unknown_option ``` * Use `HTTP2::Connection#closed?` internally (instead of `#state`) to check for connection state; this will, in a future release of `http-2`, seamlessly support the new `:closing` state. * Add missing `response` attribute reader to `HTTPX::RequestTimeoutError`. * Improve the correctness of calling `#dup` on requests and connections. ## Bugfixes * `:auth` plugin: generate token first, then set the "expires_at" timestamp (bearer tokens, specially if JWT, may carry information about when it expires). * `:auth` plugin: do not check for token freshness on a retry, instead force token regeneration. * `:retries` plugin: do not apply "retry after" delay after a ping timeout error (the ping timeout already implies a delay, so retry on a new connection should be immediate). * `:retries` plugin: do not retry on any HTTP/2 frame error (only on GOAWAY or PING frame errors). * `:persistent` plugin: do not decrement request remaining retries on ping or GOAWAY frame errors. * `:tracing` plugin: set connection initialization time to nil no termination (so that it doesn't get reused on persistent connections after reuse). * `:follow_redirects` plugin: fixed issue when a timeout error would be raised but only bubbles up to the root request, not properly closing the in-flight follow up request, and leaving the request handling phase in a broken state. * datadog adapter: the connection initialization time is now set only on connect or first request received, the reason being, making it more accurate. * webmock adapter: `.to_timeout` helper will make the request raise a `HTTPX::RequestTimeoutError` instead of a plain `TimeoutError` (otherwise, if using persistent sessions, it'd trigger a retry instead and mess with webmock request count bookkeeping). * native resolver: do not transition to `:open` if the socket was closed during resolution (which happens when an error is raised while the query bytes are buffered). * fix for when setting a new session callback on an ssl context object which has been frozen after the first connection attempt (done by binding the ssl context callback to an internal ivar which can be changed). * connection: protect against `Errno::ETIMEDOUT` errors on socket close by forcing transition to closed. * do not set a ping timer for HTTP/1.1 on keep-alive flow, as there's no ping and the connection is reestablished. # 1.8.1 ## Improvements * the session will now eagerly write initial data to connections instead of waiting for I/O the first time (saves a syscall). * removed all rescue blocks rescuing `StandardError` internally; this could interfere with usages of `httpx` inside `Timeout.timeout` blocks, which may emit an exception at any point, including in blocks where that exception could be rescued, leaving the session in a potentially irrecoverable state and looping. * debug logs change the display of ids from 'tid:123, fid:123' to 'tid=123 fid:123'. * and when using the `datadog` adapter, all related correlation ids (trace id, span id, etc) will also be added to the identifiers in the same format * plugins built on top of the `:retries` plugin will skip the `retry_after` interval when certain conditions are met. * `:persistent` plugin: request will be retried immediately, when the error happens after the keep alive interval expired. * `:auth` plugin: request will be retried immediately if it failed due to a "401 Unauthorized Error". * `:ssrf_filter` plugin: removed public/private references of exception message. ## Bugfixes * `:auth` plugin: handle edge case where `:auth_header_expires_at` returns no value. * `:digest_auth` plugin: do not retry if there was an issue building the authorization header after the probe. * `webmock` adapter: prevent mocked requests from opening a connection to the peer server that will not be used. * clear and cancel request timers on completion or reset, ensuring that they won't be retained way past the point where the request is gone. * connection: cancel and discard ping timer before closing (removes timer reference) * connection: fix logic where purging-while-resending requests to a coalesced connection was leaving references in the old connection. * moved an `on_body_chunk` callback to the `:callbacks` plugin, where it's used and expected to be defined. * `http2`: avoid closing the connection on internal errors which are supposed to be specific to a request, such as the max headers or max response body size checks. * system resolver will use an internal exception when using `Timeout.timeout` on resolutions to avoid conflicts with the default timeout exception class. * prevent edge case where `#alpn_protocol` was being called on a `TCPSocket`. * fixed v1.8.0 regression causing connection to loop when an error happens while connecting. * resolver cache: fixed cache eviction logic, where alias answers weren't being evicted, causing resolutions to stall after a certain number of resolutions.

1 0

[ruby-talk:444861] [ANN] http-2 1.3.0 released
by Tiago Cardoso 14 Oct '26

14 Oct '26

http-2 1.3.0 has been released. https://github.com/igrigorik/http-2 Pure Ruby, framework and transport agnostic, implementation of HTTP/2 protocol and HPACK header compression with support for: * [Binary framing](https://hpbn.co/http2/#binary-framing-layer) parsing and encoding * [Stream multiplexing](https://hpbn.co/http2/#streams-messages-and-frames) and [prioritization](https://hpbn.co/http2/#stream-prioritization) * Connection and stream [flow control](https://hpbn.co/http2/#flow-control) * [Header compression](https://hpbn.co/http2/#header-compression) and [server push](https://hpbn.co/http2/#server-push) * Connection and stream management * And more... see [API docs](https://www.rubydoc.info/gems/http-2) Protocol specifications: * [Hypertext Transfer Protocol Version 2 (RFC 7540)]( https://httpwg.github.io/specs/rfc7540.html) * [HPACK: Header Compression for HTTP/2 (RFC 7541)]( https://httpwg.github.io/specs/rfc7541.html) Here are the updates since the last release: ## 1.3.0 ### Improvements * PRIORITY frame handling will create the stream object, but not yielded it to the user via the `:stream` callback; it'll eventually be yielded by the time the corresponding HEADERS frame comes in. * internally, settings are stored in struct objects, which improve memory usage and methods lookups when compared to the previous Hash representation, and should reduce the potential for typos. ### Bugfixes * Fixed handling of the SETTINGS_HEADER_TABLE_SIZE setting, which besides setting the max table size on the wrong encoder, was doing so without sending back the table size update in the subsequent header block. * The SETTINGS_MAX_HEADER_LIST_SIZE setting is now enforced, gating the header block decoding flow; the setting renegotiation is therefore not ignored anymore. * PUSH_PROMISE streams are now disallowed for clients, and discarded when SETTINGS_ENABLE_PUSH is set to 0 on servers. It also respects the SETTINGS_MAX_CONCURRENT_STREAMS setting. ### Internal changes * `HTTP2::Compressor` and `HTTP2::Decompressor`'s `#table_size=` method renamed to `#max_table_size=`. It's an API breaking change, but from components considered internal to the core. ### Chore * HPACK conformance tests were (re)added to the test suite. ## 1.2.3 ### Improvements Connection and HPACK settings are now kept in a Settings container object, a struct-like class; this improves storage of settings (Struct objects use less memory than Hashes), reduces allocations (previously, some of the hashes had to merge with defaults downstream), and improves lookups (Struct accessors > Hash lookups). ### Bugfixes * h2c initiated streams will now correctly close the request stream for body-less (like-GET) requests. * negative stream ids are now checked against. * negative or 0 WINDOW_UPDATE increments are now checked against. * memory leak fixed around streams recently closed bookkeeping. ### Chore LICENSE file was accidentally left out of previous release bundles. ## 1.2.2 ### Bugfixes * allow completion of streams lower than last stream id after receiving a GOAWAY frame for stream 0 (connection), in conformance with RFC 9113 Section 6.8. * in the process, a new connection state, `:closing`, has been introduced, to identify connections which do not accept new streams BUT allow existing streams to be processed to completion, and will also process control-flow frames to aid in the process. A note that the public API `HTTP2::Connection#closed?` will also return true for that new state (besides `:closed`). * local and remote SETTINGS_MAX_CONCURRENT_STREAMS setting is now enforced correctly, i.e. the client should not allow the creation of new streams based on the remote setting, whereas the local setting will be applied by the server side when activating a stream. ## 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).

1 0

[ruby-talk:444860] The Smart Rubyist #1: I prefer to be in the top 10% developers who train AI with new ideas
by Andy Maleh 13 Oct '26

13 Oct '26

The Smart Rubyist #1: I prefer to be in the top 10% developers who train AI with new ideas https://andymaleh.blogspot.com/2026/10/the-smart-rubyist-1-i-prefer-to-be-i…

1 0

[ruby-talk:444859] Montreal.rb September 2026: Ruby Version Managers in 2026
by Andy Maleh 29 Sep '26

29 Sep '26

The video and slides for the Montreal.rb September 2026 talk "Ruby Version Managers in 2026" have been published! Talk Description: It is often useful to install more than one Ruby version on one's machine, whether to explore newer Ruby versions before committing to them on a Rails project, or to support multiple Rails projects running on multiple Rubies. Additionally, being able to scope gems by a Ruby project can be very helpful in ensuring the safety of running a Ruby app in complete isolation from other Ruby apps. The Ruby ecosystem contains multiple Ruby Version Managers that help with installing Ruby and scoping Ruby gems by project. This talk will cover the common Ruby Version Manager options in 2026, such as RVM, RBENV, CHRUBY, and ASDF. YouTube Video : https://www.youtube.com/watch?v=UFMQOkEZUSc Presentation Slides : https://docs.google.com/presentation/d/e/2PACX-1vR_uc-FSdvKmMT0gzRRK-qJ-JSU… Blog post version : https://andymaleh.blogspot.com/2026/09/montrealrb-september-2026-ruby-versi…

1 0

[ruby-talk:444858] Dissecting DHH's RailsWorld 2026 Keynote Speech from a Software Engineering Point Of View
by Andy Maleh 28 Sep '26

28 Sep '26

Dissecting DHH's RailsWorld 2026 Keynote Speech from a Software Engineering Point Of View: https://youtu.be/VsM8Ej-em8I Video blog post: https://andymaleh.blogspot.com/2026/09/dissecting-dhhs-railsworld-2026-keyn…

1 0

[ruby-talk:444857] [ANN] rodauth-oauth 1.7.0 released
by Tiago Cardoso 22 Sep '26

22 Sep '26

rodauth-oauth 1.7.0 has been released. rodauth-oauth is a rack-compatible toolkit for building OAuth 2.0 authorization servers, as well as OpenID Authentication Providers. rodauth-oauth is certified <https://openid.net/certification/> for the following profiles of the OpenID Connect™ protocol: Basic OP, Implicit OP, Hybrid OP, Config OP, Dynamic OP, Form Post OP, 3rd Party Init OP Session Management OP, RP-Initiated Logout OP, Front-Channel OP, Back-Channel OP # as simple as rodauth do enable :oauth_authorization_code_grant # or enable :oidc end Among its features, it supports: * Authorization Code Grant * Refresh Token Grant * Implicit Grant * Client Credentials Grant * Device Code Grant * Token Revocation * Token Introspection * Auth Server Metadata * PKCE * Resource Indicators * JWT Access Tokens * mTLS Client Authentication * Assertion Framework * SAML 2.0 Bearer Assertion Grant * JWT Bearer Assertion Grant * JWT Secured authorization requests (JAR) * JWT Secured authorization response mode (JARM) * Pushed Authorization requests (PAR) * Demonstrating Proof-of-Possession at the Application Layer (DPoP) * Dynamic Client Registration * Client ID Metadata Document * OpenID * OpenID Discovery * OpenID Multiple Response types * OpenID Self Issued Tokens * OpenID Connect Dynamic Client Registration * OpenID Session Management * OpenID RP Initiated Logout * OpenID Frontchannel Logout * OpenID Backchannel Logout It can also be used with Rails (via the "rodauth-rails" gem). Website: rodauth-oauth · honeyryder <https://honeyryderchuck.gitlab.io/rodauth-oauth/> Documentation: Rodauth OAuth: OAuth 2.0 and OpenID for rodauth <https://honeyryderchuck.gitlab.io/rodauth-oauth/rdoc/> Wiki: Home · Wiki · OS / rodauth-oauth · GitLab <https://gitlab.com/honeyryderchuck/rodauth-oauth/wikis/home> CI: https://gitlab.com/honeyryderchuck/rodauth-oauth/pipeline These are the release notes since the last update: # 1.7.0 ## Features ### Client ID Metadata Document Support `rodauth-oauth` supports the Client ID Metadata Document Standard (also known as CIMD), via the `oauth_client_id_metadata_document` feature. In a nutshell, this provides a way by which a Client Application can identify itself to the authorization server, without prior dynamic client registration or other existing registration. More info about the feature [in the docs]( https://gitlab.com/os85/rodauth-oauth/-/wikis/Client-ID-Metadata-Document) ### 1.6.7 #### Improvements * Some new capabilities were built into `rodauth` recently, which `rodauth-oauth` now taps into: * plugins are now object shape friendly, by defining ivars using `rodauth`'s `:uses_instance_variables` auth method (introduced in v2.44) * `:oidc` plugin `get_oidc_param` and `get_additional_param` now have a default implementation, which raises an error (eliminates warnings). * `only_json?` auth method is no longer defined (unless the `:jwt` plugin is used). * some internal methods were now moved to private, instead of being needlessly exposed (eliminates security warnings). * a new auth method, `confidential?(oauth_application)`, was added to the `:oauth_base` plugin, which is now used internally to check in some key flows whether the OAuth client application is a public or a confidential client, as it's defined in the OAuth RFC: * when using the `:oauth_dynamic_client_registration` plugin, a client secret won't be generated for public clients (same logic will be applied for client registration management endpoints). * when using the `:oauth_application_management` plugin, default templates will include a client type column, and omit the client secret for public clients, where they would previously. #### Bugfixes * do not render null fields in the payload of the oauth server metadata endpoint (RFC 8414 section 2 requires omission of undefined values, so clients can apply the recommended defaults). * fixed regexp used for json requests (same fix as in [rodauth]( https://github.com/jeremyevans/rodauth/commit/3e0d7ab2d49a5733d1afcaaf1062b… )) ### 1.6.6 #### Improvements * Authorization form params will now be exposed to the HTML rendering via the `rodauth.authorize_form_params`; this not only reduces the size of the bundled forms, but also makes it much easier to add or remove features with their own required authorize params. * `:oauth_jwt_base` feature: new `:oauth_jwt_iat_leeway` option (defaults to 30, as in seconds), is used now to make the JWT claim `iat` claim tolerant to clock skew. This option is used in both the `jwt` and `json/jwt` gem integrations. * `:oauth_pkce` feature: new `:oauth_pkce_allow_plain_method` option, which may disallow the usage of `"plain"` as a PKCE challenge method * defaults to `true` in order not to break backwards compatibility, but this is going to change in a future version, so you are recommended to set it explicitly in order not to break your application in a future upgrade. #### Bugfixes * (critical) `:oauth_dynamic_client_registration` feature: `PUT /register` was incorrectly authenticating the request (responding with 200 when secret didn't match), thereby allowing anyone (else) to update application parameters. * (critical) `:oauth_dynamic_client_registration` feature: `PUT /register` was not hashing the client secret when hashing on the client secret was enforced. * `:oauth_authorization_code_grant` feature: escape untrusted values in the authorize form (hidden request params, the `"state"` in the cancel link, the client application name), in the authorize form post POST response form, and in the device verification template. * token endpoint: enforce 4XX HTTP responses with JSON encoded body when there are errors (instead of making it rely on the "accept" HTTP header). * client authentication: fallback to `oauth_default_token_endpoint_auth_methods` when the application being authentication has no `token_endpoint_auth_method` set (instead of assuming it as "none"). * `:oauth_dynamic_client_registration` feature: client metadata which the server does not understand is now ignored (RFC 7591 section 3.1), instead of failing the registration with an `"invalid_client_metadata"` error. * `:oauth_dynamic_client_registration` feature: fix typo which was exposing `client_secret` in the registration response in cases where it shouldn't. * `:oauth_dynamic_client_registration` feature: emit `"client_id_issued_at"` as epoch seconds instead of an ISO8601 string, as per [RFC 7591](https://datatracker.ietf.org/doc/html/rfc7591#section-3.2.1). * `:oauth_dynamic_client_registration` feature: remove "registration_access_token" and "registration_client_uri" parameters from the payload (these are only valid for the OIDC counterpart). * `json/jwt`: decoding a JWT was bypassing claims verification. #### Security * Using `rodauth` `timing_safe_eql?` helper method, a string comparison function which is safe against timing attacks, in client secret matching and PKCE verification. ### 1.6.5 #### Bugfixes * `:oauth_dynamic_client_registration` feature: scoping to the client being updated, preventing thst the resulting database operations touch every row in the `"oauth_applications"` table. * `:json` feature: fixed implementation of `json_request?`. * `json-jwt` support: set explicit `:skip_verification` parameter when the jwt decoding algorithm is `"none"`. * rails generators: add missing uniqueness constraint to the index on the `"issuer"` column of the `"oauth_saml_settings"` table. * rails generators: remove the `"jti"` column entry from the `"oauth_dpop_proofs"` table (already made the pkey in the `create_table` instruction). * Make `password_hash` method public, which restores compatibility with `rodauth` v2.28 or more recent; `rodauth` **minimum supported version** becomes 2.28.0 as a result, which should not be perceived as a breaking change, as there are no other significant API changes, and ruby version support remains the same.

1 0

[ruby-talk:444856] JRuby 10.1.2.0 released
by Charles Oliver Nutter 21 Sep '26

21 Sep '26

The JRuby community is pleased to announce the release of JRuby 10.1.2.0. * Homepage: [https://www.jruby.org/](https://www.jruby.org/) * Download: [https://www.jruby.org/download](https://www.jruby.org/download) JRuby 10.1.x targets Ruby 4.0 compatibility. Thank you to our contributors this release, you help keep JRuby moving forward! [@aminmansuri], [@drzaiusx11], [@evaniainbrooks], [@gillesbergerp], [@jcharaoui], [@jwils], [@kares], [@lloeki], [@makenowjust], [@nobu], [@sampokuokkanen], [@shugo] Notable Changes --------------- ### Compatibility * Multiple fixes for fibers and fiber scheduler support. [#9604], [#9607], [#9622], [#9645], [#9649], [#9656], [#9660] ### Performance * Fixed a regression in startup time on MacOS by properly loading native JNR subsystem. [#9690] * Improve performance of Ruby subclasses of Java classes. [#9619], [#9557] * Improve performance of autoloads overridden by an actual require. [#9677] ### Java Integration * The location of the AppCDS JSA file can now be specified with JRUBY_JSA_HOME. [#9667] ### Standard Library * Update to jar-dependencies 0.6.1 using mima for dependency resolution instead of the ruby-maven gem. [#9515], [#9720] * Update default and bundled standard library gems. [#9705] #### Default gems * erb 6.0.7 * error_highligh 0.7.2 * ffi 1.17.4 * io-console 0.9.4 * ipaddr 1.2.9 * jruby-openssl 0.16.2 * json 2.21.2 * net-protocol 0.4.0 * pp 0.6.4 * psych 5.5.0 * resolv 0.8.0 * strscan 3.1.8 * syntax_suggest 3.0.0 * timeout 0.6.1 * win32-registry 0.1.2 #### Bundled gems * bigdecimal 4.1.2 (ruby parts only) * csv 3.3.6 * minitest 5.27.0 * net-imap 0.6.7 * nkf 0.3.0 * pstore 0.2.1 * rdoc 7.2.0 * reline 0.7.0 * resolv-replace 0.2.0 * rss 0.3.3 * test-unit 3.7.8 ### 76 Issues and PRs resolved for 10.1.2.0 https://www.jruby.org/2026/09/21/jruby-10-1-2-0 *Charles Oliver Nutter* *Architect and Technologist* Headius Enterprises https://www.headius.com headius(a)headius.com

1 0

[ruby-talk:444855] JRuby 10.0.7.0 released
by Charles Oliver Nutter 21 Sep '26

21 Sep '26

The JRuby community is pleased to announce the release of JRuby 10.0.7.0. * Homepage: [https://www.jruby.org/](https://www.jruby.org/) * Download: [https://www.jruby.org/download](https://www.jruby.org/download) JRuby 10.0.x targets Ruby 3.4 compatibility. Thank you to our contributors this release, you help keep JRuby moving forward! [@aminmansuri], [@evaniainbrooks], [@gillesbergerp], [@jwils], [@kares], [@lloeki] Notable Changes --------------- ### Performance * Fixed a regression in startup time on MacOS by properly loading native JNR subsystem. [#9688], [#9689] * Improve performance of autoloads overridden by an actual require. [#9677], [#9675] ### Java Integration * The location of the AppCDS JSA file can now be specified with JRUBY_JSA_HOME. [#9667] ### Standard Library ### Default gems * jruby-openssl 0.16.2 [#9538], [#9561] * resolv 0.7.2 [#9637], [#9641] ### 53 Issues and PRs resolved for 10.0.7.0 https://www.jruby.org/2026/09/21/jruby-10-0-7-0 *Charles Oliver Nutter* *Architect and Technologist* Headius Enterprises https://www.headius.com headius(a)headius.com

1 0

[ruby-talk:444854] Ptero Pro AI Chat — Now with a Developer API
by amine kheddache 20 Sep '26

20 Sep '26

Hello Ruby Community, I'm Amine KHD, maintainer of Ptero Pro AI Chat, a free open-source AI chat platform. I wanted to share that Ptero now has a developer API, so you can integrate AI chat and other tools directly into your Ruby applications using a simple REST interface.. What the API offers: - Access to multiple models (DeepSeek, Qwen, Mercury, and more) - Free to use — no credit card, Example use case: You could build a Ruby helper that uses the API to explain code, generate tests, or debug errors directly in your development workflow. Try it here: https://ptero.pro Source code: https://github.com/aminkheddache-dotcom/Ptero It's completely free and will always be free. If you find it useful, feedback is always welcome. Best regards, Amine KHD Founder & Lead Developer, Ptero aminekhd(a)ptero.pro https://ptero.pro

1 0

[ruby-talk:444853] [ANN] sexp_processor 4.17.6 Released
by Ryan Davis 20 Sep '26

20 Sep '26

sexp_processor version 4.17.6 has been released! * home: <https://github.com/seattlerb/sexp_processor> * rdoc: <http://docs.seattlerb.org/sexp_processor> sexp_processor branches from ParseTree bringing all the generic sexp processing tools with it. Sexp, SexpProcessor, Environment, etc... all for your language processing pleasure. ## Features/Problems: * Includes SexpProcessor and CompositeSexpProcessor. * Allows you to write very clean filters. * Includes MethodBasedSexpProcessor * Makes writing language processors even easier! * Sexp provides a simple and clean interface to creating and manipulating ASTs. * Includes new pattern matching system. Changes: ### 4.17.6 / 2026-09-20 * 2 bug fixes: * Improved coverage to 100% for some modules. More to go. Fixed some minor problems. * Minor cleanup in SexpProcessor.

1 0