The previous revision still used SSSE3 instructions on MSVC x64 without checking the CPU, which clang-cl rejects, so the clang-cl build stopped in the prism extension. ruby/prism@1bab98e441 switched to SSE2.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
prism is no longer a default gem (the built-in parser is Ruby::Prism
now), so add the prism gem to gems/bundled_gems. `require "prism"`
keeps providing the gem, which can be any version. lib/bundled_gems.rb
warns when it is required under bundler without a Gemfile entry, like
other gems promoted to bundled gems.
The gem is pinned to the upstream revision that ruby/ruby is synced
with, because the tests of the released 1.9.0 compare with the parser
of the running Ruby, whose grammar has moved on in 4.1.
prism does not keep its templated files in git, so BundledGem.build
(used by both common.mk and defs/gmake.mk) generates them before
building the gem from the checkout. Since the gem built from the
revision has the same version as the released one, BundledGem.unpack
now clears the target directory first; otherwise files removed upstream
(ext/prism/api_pack.c) remain from the released gem and break the
build.
tool/test-bundled-gems.rb: several bundled gems (irb, rdoc, rbs,
typeprof, ...) require prism, and their tests spawn ruby with
--disable=gems, where the prism gem is not loadable anymore. Preset its
load paths in RUBYLIB, as is already done for debug.
[Bug #22379]
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The bundled_gems workflow has failed every day since 2026-08-16 because
rbs 4.0.3's Ripper_test.rb no longer finds Ripper on master. rbs 4.2.0
picks up the upstream fix that requires "ripper" in the stdlib tests.
typeprof 0.32.0 never finishes load_core_rbs against rbs 4.2.0, so it is
pinned to a master revision until the next release, and the newly added
collection_install test is skipped because rbs's bundle_install helper
runs whichever bundle comes first on PATH.
The pin at 20d4f2c3 was added to run net-imap tests against a
SimpleCov 1.0.0 compatible helper. With coverage disabled for bundled
gem tests, the released gem can be used directly.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>