ruby.git/test, branch v4.0.3

[ruby/erb] Prohibit def_method on marshal-loaded ERB instances

2026-04-21T08:16:04+00:00

Extends the @_init guard to def_method so that an ERB object created
via Marshal.load (which bypasses initialize) raises ArgumentError
instead of evaluating arbitrary source. def_module and def_class both
delegate to def_method and are covered by the same check.

Co-authored-by: Tristan Madani

merge revision(s) 08372635f7ec09f7115bd254246ebd637499651c: [Backport #21926]

2026-03-16T18:57:04+00:00

	Fix race condition right after ubf registration

	Fixes [Bug #21926]

merge revision(s) f315d250b44e75a1a69f4a05b293dcc701377689: [Backport #21947]

2026-03-16T18:56:14+00:00

	[ruby/timeout] Compatibility with Fiber scheduler.
	(https://github.com/ruby/timeout/pull/97)

	[Bug #21947]

merge revision(s) 55694ad7efc3f8dc6d5c7aefa60ded4c303ed6cf: [Backport #21945]

2026-03-16T18:55:53+00:00

	[Bug #21945] Correctly handle `and?` and similar

YJIT: Fix not reading locals from `cfp->ep` after `YJIT.enable` and exceptional entry

2026-03-16T18:03:25+00:00

[Backport #21941]

In case of `--yjit-disable`, YJIT only starts to record environment
escapes after `RubyVM::YJIT.enable`. Previously we falsely assumed that
we always have a full history all the way back to VM boot. This had YJIT
install and run code that assume EP=BP when EP≠BP for some exceptional
entry into the middle of a running frame, if the environment escaped
before `YJIT.enable`.

The fix is to reject exceptional entry with an escaped environment.
Rename things and explain in more detail how the predicate for deciding
to assume EP=BP works. It's quite subtle since it reasons about all
parties in the system that push a control frame and then run JIT code.

Note that while can_assume_on_stack_env() checks the currently running
environment if it so happens to be the one YJIT is compiling against, it
can return true for any ISEQ. The check isn't necessary for fixing the
bug, and the load bearing part of this patch is the change to
exceptional entries.

This fix is flat on speed and space on ruby-bench headline benchmarks.

Many thanks for the community effort to create a small test case for
this bug.

Use $LOAD_PATH.replace for safer restoration in test

2026-03-12T00:42:58+00:00

Co-Authored-By: Claude Opus 4.6

Suppress bundled gems warning for subfeatures found outside stdlib [Bug #21828]

2026-03-12T00:42:58+00:00

Co-Authored-By: Claude Opus 4.6

Merge zlib-3.2.3

2026-03-09T15:19:27+00:00

[ruby/prism] Fix in handling

2026-03-06T17:02:23+00:00

in is a unique keyword because it can be the start of a clause or
an infix keyword. We need to be explicitly sure that even though in
_could_ close an expression context (the body of another in clause)
that we are not also parsing an inline in. The exception is the
case of a command call, which can never be the LHS of an expression,
and so we must immediately exit.

[Bug #21925]
[Bug #21674]

https://github.com/ruby/prism/commit/20374ced51

[ruby/prism] Fix error message for block/lambda with `...` argument

2026-03-06T17:02:23+00:00

They currently complain that the parent method is not forwarding.
But the actual problem is that these types of arguments simply don't
accept `...`

Fixes [Bug #21927]

https://github.com/ruby/prism/commit/0aa2363331