Ruby Issue Tracking System

07/29/2026

11:24 PM Ruby Revision 8495d0ec (git): win32/rm.bat: report removal failures via exit code

The `error` variable was set on failure but never reached the exit
code, so removal failures such as a locked DLL left `nmake clean`
green while stale artifacts remained. Exit with `error` at the end.
Since `rd /s` does not set ERRORLEV... hsbt (Hiroshi SHIBATA)

11:23 PM Ruby Revision ba576930 (git): [ruby/rubygems] Fail `bundle check` when frozen mode needs lockfile changes

`BUNDLE_FROZEN=1 bundle check` reported that dependencies are satisfied and exited 0 even when the lockfile was missing CHECKSUMS entries, because `write_lock` only warns in frozen mode. Run the same frozen validation as `bundle install`... hsbt (Hiroshi SHIBATA)

04:44 AM Ruby Revision e86de2aa (git): [ruby/rubygems] Pin cross-platform cooldown exclusion in an e2e spec

Exclusion is keyed on [name, version] and deliberately ignores
platform, so pushing a fresh platform-specific build under an
already-ripe version number cannot slip new code past the cooldown.
No spec covered that behavior.
https://gith... hsbt (Hiroshi SHIBATA)

04:44 AM Ruby Revision 0de0afb2 (git): [ruby/rubygems] Assert on the lockfile in the cooldown bypass control spec

On x86_64-linux hosts `--cooldown 0` resolves to the platform-specific
build, so `include_gems` failed expecting the ruby platform.
https://github.com/ruby/rubygems/commit/d7be25160e
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> hsbt (Hiroshi SHIBATA)

04:44 AM Ruby Revision 011591a0 (git): [ruby/rubygems] Add --cooldown flag to bundle lock and bundle cache

Both commands resolve, but only install, update, add and outdated
accepted the flag, so the resolver's failure hint suggesting
`--cooldown 0` was not actionable on `bundle lock --update`.
https://github.com/ruby/rubygems/commit/2c4f4f39... hsbt (Hiroshi SHIBATA)

07/28/2026

05:23 AM Ruby Revision fdf6dba1 (git): [ruby/rubygems] Regenerate man pages

https://github.com/ruby/rubygems/commit/6c1bf4b7d1 hsbt (Hiroshi SHIBATA)

05:23 AM Ruby Revision bbb8e912 (git): [ruby/rubygems] Clarify that Gemfile :path points to unpacked gem sources

The :path option was misread as a way to install a packaged .gem
file. State explicitly that it expects a directory with the gem's
unpacked source code.
https://github.com/ruby/rubygems/commit/dc7fdaa2a6 hsbt (Hiroshi SHIBATA)

05:23 AM Ruby Revision 58cf248b (git): [ruby/rubygems] Link bundle-platform(1) to the PLATFORMS section of gemfile(5)

The detailed explanation of platforms lives in gemfile(5), but
bundle-platform(1) never pointed readers there.
https://github.com/ruby/rubygems/commit/0af79d82ff hsbt (Hiroshi SHIBATA)

04:46 AM Ruby Bug #18947: Unexpected Errno::ENAMETOOLONG on Windows

https://github.com/ruby/ruby/pull/18088 hsbt (Hiroshi SHIBATA)

02:31 AM Ruby Bug #18947: Unexpected Errno::ENAMETOOLONG on Windows

There is another way that does not need the registry key. Go's runtime sets the undocumented `IsLongPathAwareProcess` bit (0x80 at PEB offset 3) at startup, which `RtlAreLongPathsEnabled` reads, so long paths work per-process regardless ... hsbt (Hiroshi SHIBATA)