Activity
From 12/25/2025 to 12/31/2025
Today
-
05:47 PM Revision 7cf6cc83 (git): Register imemo_ment as a pinning object
- It sometimes pins itself when it is in the overloaded_cme table.
-
02:56 PM Revision b27d9353 (git): Use `is_obj_encoding` instead of `is_data_encoding`
- The argument to `is_data_encoding` is assumed to be `T_DATA`.
-
- This makes it easier to visualize in profilers which one is non-parallel.
https://github.com/ruby/mmtk/commit/ba68b2ef3b -
- This commit allows objects that are safe to be freed in parallel to do so.
A decrease in object freeing time can be seen in profiles.
The benchmarks don't show much difference.
Before:
-------------- -------------------- ---------- ... -
- A plain `char` may be `signed` or `unsigned` depending on the
implementation. Also, bitwise ORing of `signed` values is not
guaranteed to be `signed`. To ensure portability, should logical-OR
each comparison, but casting to `signed c... -
10:16 AM Feature #21721 (Rejected): Allow `Queue` and `SizedQueue` to be used as LIFO queues
-
- Alright. I'll close this for now, and consider opening a feature request for `Thread::Stack`.
- 10:07 AM Revision c97f5d59 (git): [ruby/json] Simplify unescape_unicode
- https://github.com/ruby/json/commit/976ba36629
Co-Authored-By: Jean Boussier <jean.boussier@gmail.com> - 09:54 AM Revision 61d45c85 (git): [ruby/json] Keep track of the the number of additional backslashes to avoid an extra memchr searching the remaining characters when no more backslashes exist.
- https://github.com/ruby/json/commit/d21d9362fa
-
- The flags for `rb_data_type_t::flags` are public constants for
defining `rb_data_type_t`. The embedded data flag and mask are
internal implementation detail. -
08:00 AM Feature #8948: Frozen regex
- matz (Yukihiro Matsumoto) wrote in #note-35:
> I still do not see enough benefit in putting in incompatible changes. Even if we can rewrite all the gems, we will still have incompatibility issues in user applications.
It seems extrem... -
03:33 AM Feature #8948: Frozen regex
- Eregon (Benoit Daloze) wrote in #note-34:
> @matz Is it OK to merge https://github.com/ruby/ruby/pull/14547 now for 4.1?
I still do not see enough benefit in putting in incompatible changes. Even if we can rewrite all the gems, we wi... -
- Probably it's because of commit:c970d2941d56a862bb9bb3b808cb588c2982f436.
That is the indent is not related, but the behavior change. -
03:53 AM Bug #21816 (Open): iseq code_location of proc changed
- TBH, I'm not really sure if that title matches the problem here, but I can produce this issue with the following test:
```ruby
# bug.rb
# note the indentation of the callable
callable = -> { puts "Hello, World!" }
iseq = Rub... -
- It should not be exposed because it is so implementation specific that
it is only used in gc.c even within the entire Ruby source tree. -
- The combination of `&` and `&&` is confusing.
12/30/2025
-
09:44 PM Misc #21804: Getting setup-ruby Earlier
- I left some thoughts in the PR, but will post here to keep discussion in one place.
> Thanks for taking the time to open this PR to move the discussion forward, even though you’re understandably skeptical of the approach. I share your... -
- Earlopain (Earlopain _) wrote in #note-6:
> But I think the bigger issue here is that windows builds are not first-party. So even if the release process gets adapted, issues like what [@mdalessio (Mike Dalessio)](/users/443) wrote above... -
- Eregon (Benoit Daloze) wrote in #note-2:
> So I think this is something to add to the post-release checklist:
@hsbt Would you be willing to do those steps when releasing a new version? Is there a public release checklist somewhere?
Othe... -
- Earlopain (Earlopain _) wrote in #note-6:
> I don't really see the point of automerging PRs when someone still has to create the release manually. Merging the PRs is not much effort, someone just needs to do it.
I meant the release w... -
07:58 PM Misc #21804: Getting setup-ruby Earlier
- I don't really see the point of automerging PRs when someone still has to create the release manually. Merging the PRs is not much effort, someone just needs to do it.
Having this happen as part of release management sounds reasonable... -
03:51 PM Misc #21804: Getting setup-ruby Earlier
- > Maybe it'd make sense and possibly safe enough to automatically merge PRs by ruby-builder-bot, after they pass CI of course ... if someone is interested, please make a PR to setup-ruby.
I've opened https://github.com/ruby/setup-ruby... -
> https://github.com/ruby/setup-ruby/pull/844 got merged the same day, what would you expect?
A counter-example, though, is that the PR for windows support (https://github.com/ruby/setup-ruby/pull/847) took 3 days to get merged.
I thi...-
- Maybe it'd make sense and possibly safe enough to automatically merge PRs by `ruby-builder-bot`, after they pass CI of course.
I'm not sure how feasible that is (e.g. is there a GHA event triggered when CI has passed?), but if someone is... -
- https://github.com/ruby/setup-ruby/pull/844 got merged the same day, what would you expect?
Concretely I currently merge setup-ruby PRs and I have told @hsbt in the past he can merge (+ release) for new added versions.
More people co... -
- * [Feature #8948] Frozen regex (eregon)
* Can we merge it now for 4.1? Then there is plenty of time for the few gems that rely on mutable Regexp to adapt.
* We can also revert it if it turns out to be too disrupting. -
- @matz Is it OK to merge https://github.com/ruby/ruby/pull/14547 now for 4.1?
Then there is plenty of time for the few gems that rely on mutable Regexp to adapt.
BTW I noticed someone else also did a PR for this, so there seems to be ... -
- https://github.com/ruby/mmtk/commit/290a2aec4e
-
-
-
-
- Thanks, good find! I have a fix here: https://github.com/ruby/ruby/pull/15772
-
05:44 AM Feature #21084 (Open): Declare objects have weak references
- I don't think this works correctly with generational GC. This crashes reliably on HEAD (works fine on 4.0.0)
``` ruby
wmap = ObjectSpace::WeakMap.new
GC.disable # only manual GCs
GC.start
GC.start
retain = []
50.times do
... -
-
- Fixes issue pointed out in https://bugs.ruby-lang.org/issues/21084#note-7.
The following script crashes:
wmap = ObjectSpace::WeakMap.new
GC.disable # only manual GCs
GC.start
GC.start
retain = []
50.times do
... -
- Applied in changeset commit:git|c970d2941d56a862bb9bb3b808cb588c2982f436.
----------
[Bug #21784] Fix the Proc#source_location start_column for stabby lambdas
* Consistent with plain `blocks` and `for` blocks and methods
where the so... -
- Applied in changeset commit:git|cd66d15858a06406d1de854f3e9690d3557a9864.
----------
[Bug #21783] Fix documentation of {Method,UnboundMethod,Proc}#source_location -
- Applied in changeset commit:git|d82fc3360d7cfa7e1e1a4dddb668b4c38808538a.
----------
Reapply "[Feature #6012] Extend `source_location` for end position
* This reverts commit 065c48cdf11a1c4cece84db44ed8624d294f8fd5.
* This functionalit... -
- * See https://github.com/ruby/ruby/pull/15580
-
-
- * Consistent with plain `blocks` and `for` blocks and methods
where the source_location covers their entire definition.
* Matches the documentation which mentions
"where the definition starts/ends".
* Partially reverts d357d50f0a7440... -
-
- * This reverts commit 065c48cdf11a1c4cece84db44ed8624d294f8fd5.
* This functionality is very valuable and has already taken 14 years
to agree on the API.
* Let's just document it's byte columns (in the next commit).
* See https://bugs.... -
-
- [GH-15737] needs to be backported to the 4.0 branch.
[GH-15737]: https://github.com/ruby/ruby/pull/15737 -
- Applied in changeset commit:git|19e539c9ee1701b34189fa0c1feb942adeb0e326.
----------
[Bug #21814] Fix negative bignum modulo
If modulo is zero, do not apply bias even if the divisor is zero.
`BIGNUM_POSITIVE_P` is true even on bignum ... -
- [GH-15771](https://github.com/ruby/ruby/pull/15771)
-
- When I try `0.pow(2,-9999999999999999990)`, irb prints `-9999999999999999990`, but I think no matter what you divide zero by, the modulo should be zero.
Matz.
-
- If modulo is zero, do not apply bias even if the divisor is zero.
`BIGNUM_POSITIVE_P` is true even on bignum zero. - 01:31 PM Revision 966dbba8 (git): Box: skip checking the current box is the root box
- Because checking the current box is not a cheap process.
-
-
-
- This might be useful for `A`, `a`, and `Z` as well.
Updated the PR [GH-15647] to use `^` with the tests.
[GH-15647]: https://github.com/ruby/ruby/pull/15647 - 08:06 AM Revision d5af8d78 (git): Box: allocate classes as boxable when it happens in the root box
- Without this change, classes (including iclass) are allocated
as un-boxable classes after initializing user boxes (after starting
script evaluation). Under this situation, iclasses are created as
un-boxabled class when core modules are i... -
06:24 AM Feature #21797: Make Etc.nprocessors cgroup-aware on Linux
- Thank you for the summary!
I'll open a separate ticket for auto-adjusting `RUBY_MAX_CPU`.
Come to think of it, `RUBY_MAX_CPU` may have different requirements from `Etc.nprocessors` (defaulting to max # of processors may be suboptimal... -
12:22 AM Feature #21813 (Open): Add [:forward, :...] symbol tuple to indicate forwarding arguments when calling `Method#parameters`
- When accessing `Method#parameters` for a method using forwarding parameters, an unexpected behavior arises:
```ruby
def foo(*, **, &)
binding.eval "print(#{(method(__method__).parameters.dig(0,1))})" # Works fine
end
foo(1,2,3...
12/29/2025
-
04:42 PM Bug #21812 (Assigned): Kernel#sleep without arguments returns immediately when subprocess exits in another thread (regression in Ruby 4.0)
- Thanks for the nice catch.
`git bisect` points to commit:8d8159e7d87e4fd1594ce2fad3d2653e47fb1026. The changes in that commit seem relevant to this issue.
@luke-gru Could you take a look? -
04:12 PM Bug #21812 (Assigned): Kernel#sleep without arguments returns immediately when subprocess exits in another thread (regression in Ruby 4.0)
- **Description**
In Ruby 4.0.0, Kernel#sleep without arguments returns 0 immediately when a subprocess (spawned via backticks in another thread) exits. This is a regression from Ruby 3.4.8 where sleep blocks indefinitely as expected.
... -
- `compact_child_nodes` allocates an array. We can skip that step by simply yielding the nodes.
Benchmark for visiting the rails codebase:
```rb
require "prism"
require "benchmark/ips"
files = Dir.glob("../rails/**/*.rb")
results = file... -
02:12 PM Revision 14fbcf0e (git): [ruby/prism] Report missing end errors at opening token
- This commit adds an `expect1_opening` function that expects a token and
attaches the error to the opening token location rather than the current
position. This is useful for errors about missing closing tokens, where
we want to point to ... -
- https://github.com/ruby/prism/commit/166764f794
-
- This commit implements moving Immix in MMTk, which allows objects to move
in the GC.
The performance of this implementation is not yet amazing. It is very
similar to non-moving Immix in many of them and slightly slower in others.
The be... -
-
-
-
12:41 PM Bug #21801: compile failed at 4.0.0 preview 3 and snapshot issue
- It may be worth noting that the filename x64-msvcrt-ruby400.dll indicates the use of a 64-bit msvcrt.dll runtime environment.
When trying to build master in a 32-bit msvcrt environment, I encountered a similar issue.
While I cannot d... -
07:01 AM Bug #21801: compile failed at 4.0.0 preview 3 and snapshot issue
- nobu (Nobuyoshi Nakada) wrote in #note-2:
> darkspy (gerty ken) wrote:
> ...
now i tried cross compile from mingw64 in linux for windows target. the ruby 4 still can not run:
test.rb:
$stdout.sync = true
puts "test"
ruby test.rb
... -
- `ALLOCA` with too large size may result in stack overflow.
Incidentally, this suppresses the GCC false maybe-uninitialized
warning in `product_each`.
Also shrink `struct product_state` when `sizeof(int) < sizeof(VALUE)`. -
-
-
-
-
- https://github.com/ruby/ruby/pull/15763
- 08:21 AM Revision 4e0bb58a (git): fix underflow
-
05:54 AM Revision 38701a4d (git): Remove deprecated support for to_set taking arguments
-
05:03 AM Feature #21797: Make Etc.nprocessors cgroup-aware on Linux
- > What would be the value of nprocessor in this case?, e.g. if cpu_quotais 0.5, what does nprocessors return? cpu_quota.ceil?
I think it depends on the decision, but either floor or ceil should be fine (for reference, Go’s `GOMAXPROCS... -
- In public headers, casts should be enclosed in `RBIMPL_CAST` for
compilation in C++.
12/28/2025
-
- Fixes the following compiler warnings:
random.c: In function `random_init`:
random.c:416:38: warning: `rng` may be used uninitialized in this function [-Wmaybe-uninitialized]
416 | unsigned int major = rng->version.maj... -
08:51 PM Revision d615dbf4 (git): [DOC] Japanese for multi-byte characters
-
07:58 PM Feature #21810 (Open): Enable JIT (yjit,zjit) when cross-compiling
- Hello,
Please, add support for JIT while crosscompiling. Without it, embedded system will never user JIT. Even when the arch matches, the host alias normally does not match the build alias:
build_alias='x86_64-pc-linux-gnu'
host_a... -
-
- For the precondition of `RTYPEDDATA_P` that the argument must be a
Ruby object of `::RUBY_T_DATA`. -
- Currently, root fibers of threads do not have a corresponding Ruby object
backing it by default (it does have one when an object is required, such
as when Fiber.current is called). This is a problem for the new GC weak
references design ... -
- yui-knk (Kaneko Yuichiro) wrote in #note-8:
> @matz Just clarification, do we support `a[cmd 1, 2 do end]` and `a[cmd 1, 2 do end] = 3` too? IIRC, we discussed those cases in previous devmeeting and these codes are also accepted. Howeve... -
- In any case, I am against implementing FIFO under the name Queue. I agree with having a new class.
Matz.
- 08:23 AM Revision 3fe2ebf8 (git): Remove unnecessary comparison from is_local_port_fixed (#15757)
- Simplify the conditions:
- Return false if the port is 0 or a negative number
- Return true if the port is a positive number -
05:42 AM Bug #21809: Segmentation fault when running RUBY_BOX=1 gem update --system
- This actually happens on every `gem` comamnd (`gem list`, `gem install`, etc).
-
- I get a segmentation fault when I run `RUBY_BOX=1 gem update --system`. I'm using RubyGems version `4.0.3`. I've attached the crash report log file to this issue. There is no segfault when `RUBY_BOX=0`, so this really seem like an issue ...
-
12/27/2025
-
-
-
-
11:46 AM Bug #21805: Wrong "key not found" in NoMatchingPatternKeyError when destructuring Data
- Thanks. The https://github.com/ruby/ruby/pull/15748 will fix the issue.
- 09:26 AM Revision a8c3d5e1 (git): Fix: Do not fast_fallback if local_port is explicitly specified (#15732)
- `fast fallback` cannot be used with explicitly specified local port,
because concurrent binds to the same `local_host:local_port`
can raise `Errno::EADDRINUSE`.
This issue is more likely to occur on hosts with `IPV6_V6ONLY` disabled,
be... -
- That blank line separates code visually, so continuing beyond it doesn't look nice to me.
-
07:46 AM Revision 3c9e61f5 (git): [ruby/openssl] cipher: remove incorrect assertion in Cipher#update
- Commit https://github.com/ruby/openssl/commit/1de3b80a46c2 (cipher: make output buffer String independent,
2024-12-10) ensures the output buffer String has sufficient capacity,
bu the length can be shorter. The assert() is simply incorre... - 06:53 AM Revision b8201a09 (git): Update bundled gems list as of 2025-12-27
12/26/2025
-
-
-
-
- [Feature #19630]
This dangerous behavior was removed in 4.0 (996cae65f3cc8fed60c6bb758b00882cac49389d)
but the documentation wasn't updated. -
- The underlying definition, `rb_struct_ptr`, was removed four years
ago. -
- nobu (Nobuyoshi Nakada) wrote in #note-2:
> darkspy (gerty ken) wrote:
> ...
i tryied 4.0.0 release on msys 2. same result as above -
-
-
-
-
-
-
-
-
- The backport to only 3.4 is required.
-
03:40 AM Bug #21807 (Closed): ArgumentError is reported when forwarding arguments to method with intermediate optional arguments
- In Ruby 3.4.x, `ArgumentError` is reported when forwarding arguments to a method with intermediate optional arguments.
How to reproduce:
Execute sample below.
``` ruby
class Foo
def foo(a = nil, b)
p a, b
end
end
... -
- If I recall, this is intentional. A blank line before a period for a method call also causes a parsing error.
```
$ ruby -e '"foo"
>
> ...
-e: -e:3: syntax error found (SyntaxError)
1 | "foo"
2 |
> 3 | .upcase
| ^ unexp... -
06:16 AM Bug #21808 (Assigned): Inconsistency in support of additional newlines with boolean logical operators on new line
- With this I mean the new Ruby 4 feature.
With the old style, one could add additional lines in between:
```ruby
if true &&
true
puts 'match'
end
```
With the new style, this results in a syntax error
```ruby
if true... -
-
-
-
- Include internal/error.h instead.
-
- 05:05 AM Revision b01fd2d8 (git): Fix RSET_IS_MEMBER macro parameter mismatch
- The RSET_IS_MEMBER macro had a parameter named 'sobj' but the macro
body used 'set' instead, causing the first argument to be ignored.
This worked by accident because all current callers use a variable
named 'set', but would cause compi... -
- 03:38 AM Revision 594dd8bf (git): [ruby/pp] Support private instance_variables_to_inspect
- (https://github.com/ruby/pp/pull/70)
* Support private instance_variables_to_inspect in pp
Ruby supports calling instance_variables_to_inspect even when
it is defined as a private method (ruby/ruby#13555).
This change aligns pp with R... -
03:12 AM Revision 9824724b (git): Skip test_write_binary(GemSingletonTest) at rbs tests
- ```
Errno::EACCES: Permission denied @ rb_file_s_rename
...
D:/a/ruby/ruby/src/lib/rubygems/util/atomic_file_writer.rb:42:in 'File.rename'
```
It may caused with atomic_file_writer.rb -
-
-
- 02:01 AM Revision e95a9942 (git): Update default gems list at 565ea26ad10ea8c3c6ce9bdae6cbb7 [ci skip]
-
-
-
- 02:00 AM Revision 70c7f3ad (git): [ruby/strscan] Bump version
- https://github.com/ruby/strscan/commit/747a3b5def
-
- * To find out efficiently if TCPSocket#initialize supports the open_timeout keyword argument.
https://github.com/ruby/net-protocol/commit/738c06f950 -
- https://github.com/ruby/json/commit/a5c160f372
- 02:00 AM Revision 8ccfb375 (git): [ruby/json] Update `fpconv_dtoa` definition to use `dest[32]`
- https://github.com/ruby/json/commit/4808fee9af
- 02:00 AM Revision 1f526b34 (git): [ruby/ipaddr] Follow-up fix for InvalidAddressError messages
- https://github.com/ruby/ipaddr/commit/b92ef74b91
-
02:00 AM Revision f3149af3 (git): [ruby/prism] Sync `Prism::Translation::ParserCurrent` with Ruby 4.0
- This PR updates the fallback version for `Prism::Translation::ParserCurrent` from 3.4 to 4.0.
Currently, the fallback resolves to `Parser34`, as shown below:
```console
$ ruby -v -rprism -rprism/translation/parser_current -e 'p Prism::... - 02:00 AM Revision 44a17656 (git): [ruby/timeout] add test case for string argument
- https://github.com/ruby/timeout/commit/fef9d07f44
- 02:00 AM Revision f8d0960a (git): [ruby/resolv] Handle TCP Requester #recv_reply incomplete data
- https://github.com/ruby/resolv/commit/9c640bdc4a
- 02:00 AM Revision 4b7bbd43 (git): [ruby/resolv] Fix TCP Requester #recv_reply
- https://github.com/ruby/resolv/commit/96dc3d15fe
-
-
02:00 AM Revision bdbe8d50 (git): [ruby/rubygems] Write gem files atomically
- This change updates `write_binary` to use a new class,
`AtomicFileWriter.open` to write the gem's files. This implementation
is borrowed from Active Support's [`atomic_write`](https://github.com/rails/rails/blob/main/activesupport/lib/ac... -
- https://github.com/ruby/rubygems/commit/43371085f4
-
02:00 AM Revision 80242458 (git): [ruby/date] remove conditional for uint64_t
- https://github.com/ruby/date/commit/47778c32d8
-
- https://github.com/ruby/date/commit/5e6a458179
-
- https://github.com/ruby/date/commit/2682dc79c0
-
- https://github.com/ruby/date/commit/cd7a329dfd
-
- Replace floating-point arithmetic and iterative loops with pure integer
operations for ~40% faster Date operations. Date.ordinal and Date.commercial
are ~2x faster due to O(1) first-day-of-year calculation.
Reference: https://arxiv.org/... -
- (https://github.com/ruby/stringio/pull/197)
Previous doc merely linked to `IO#read`; new doc stays local, shows
examples using `StringIO`.
https://github.com/ruby/stringio/commit/e8b66f8cdd -
- (https://github.com/ruby/stringio/pull/196)
Previous doc merely linked to `IO#putc`. The new doc stays local,
provides examples using `StringIO` objects.
https://github.com/ruby/stringio/commit/8983f32c50 -
- (https://github.com/ruby/stringio/pull/195)
Previous doc unhelpfully pointed to `IO#pread`; this PR documents
locally, with StringIO examples.
https://github.com/ruby/stringio/commit/806f3d9741 - 02:00 AM Revision 67f830e0 (git): [ruby/stringio] Development of 3.2.1 started.
- https://github.com/ruby/stringio/commit/c9cd1c9947
-
- https://github.com/ruby/mmtk/commit/f4c46cabc7
- 12:07 AM Revision 715d69ac (git): Update default gems list at a06a59e3b34cd5227363dc3af14dc6 [ci skip]
-
-
12/25/2025
-
-
-
11:39 PM Bug #21806 (Assigned): `bundler/inline` generates "uninitialized constant Gem::NameTuple" only when RUBY_BOX=1
- ## Steps to reproduce
1. Prepare a file that uses "bundler/inline"
2. Run with RUBY_BOX=1
```ruby
# issue.rb
require "bundler/inline"
gemfile(true) do
source "https://rubygems.org"
gem "json"
end
require "json"
put... -
10:46 PM Bug #21805 (Open): Wrong "key not found" in NoMatchingPatternKeyError when destructuring Data
- Consider
```
Foo = Data.define(:x)
Foo.new(1) => {x:, z:}
```
It raises `#<data Foo x=1>: key not found: :x (NoMatchingPatternKeyError)`
Clearly the message is misleading, as it is key :z that is missing. -
- In this case the update is automated and ready to be merged by the repo maintainer: https://github.com/ruby/setup-ruby/pull/844
If I may, the issue to me seems more to be like many Ruby owned projects, it's mostly a one person show, s... -
- ruby/setup-ruby is commonly used for development in OSS projects and real-world Rails applications.
https://github.com/ruby/setup-ruby
This is not specific to Ruby 4.0.0. There is often a delay between a Ruby release and the availabi... -
- Applied in changeset commit:git|10b97f52fd2cba189b8952fcb02c4d6dd9b1b6f2.
----------
Implement declaring weak references
[Feature #21084]
# Summary
The current way of marking weak references uses `rb_gc_mark_weak(VALUE *ptr)`.
This ... -
-
-
-
-
-
-
- [Feature #21084]
# Summary
The current way of marking weak references uses `rb_gc_mark_weak(VALUE *ptr)`.
This presents challenges because Ruby's GC is incremental, meaning that if the
`ptr` changes (e.g. realloc'd or free'd), then we... -
-
12:35 PM Revision 099da884 (git): test_box: avoid failure with --program-suffix (#15734)
-
06:31 AM Revision 6a66129d (git): fix the condition of www repo
-
06:03 AM Misc #21777: DevMeeting-2026-01-14
- - [Bug #21803] `Addrinfo#connect_internal` should raise `IO::TimeoutError` on user-specified timeouts
- I’d like to make `Socket.tcp` consistently raise `IO::TimeoutError` when a user-specified timeout occurs, rather than raising `Err... -
- ## Background & Proposal
`Addrinfo#connect_internal` is a core internal method that is called by both
`Addrinfo#connect` and `Addrinfo#connect_from`.
It receives a user-specified timeout value from these methods and currently raises
... -
-
- `$~` and its accessors are related to regular expressions, but are not
themselves. -
- This reverts commit 8d097bc472fc66221dee23bb8f9e0dddac16db23.
-
12:06 AM Revision 3c4cda10 (git): [DOC] Add back Rust 1.85.0 requirement to NEWS.md (#15728)
- * [DOC] Add back Rust 1.85.0 requirement to NEWS.md
Addresses k0kubun's review in https://github.com/ruby/ruby/pull/15711#issuecomment-3690541074
NEWS.md serves both CRuby developers as well as end-users. As the
release date closes in,...