Skip to content

[pull] master from ruby:master#1185

Merged
pull[bot] merged 10 commits into
turkdevops:masterfrom
ruby:master
Jul 6, 2026
Merged

[pull] master from ruby:master#1185
pull[bot] merged 10 commits into
turkdevops:masterfrom
ruby:master

Conversation

@pull

@pull pull Bot commented Jul 6, 2026

Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

dependabot Bot and others added 10 commits July 6, 2026 11:31
Bumps the github-actions group with 1 update in the / directory: [taiki-e/install-action](https://github.com/taiki-e/install-action).


Updates `taiki-e/install-action` from 2.82.7 to 2.82.9
- [Release notes](https://github.com/taiki-e/install-action/releases)
- [Changelog](https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md)
- [Commits](taiki-e/install-action@16b0581...4684b84)

---
updated-dependencies:
- dependency-name: taiki-e/install-action
  dependency-version: 2.82.9
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github-actions
...

Signed-off-by: dependabot[bot] <support@github.com>
A `for` loop index may be a multiple-assignment target whose first
element is itself a parenthesized (nested) target, e.g.

    for (a, b), c in 1..10
    end

CRuby's parse.y accepts this, and a plain multiple assignment with the
same target (`(a, b), c = ...`) is accepted, but Prism rejected it with
"unexpected write target".

When parse_parentheses finishes the first `(a, b)`, it validates the
multi-target it produced. In a `for` index it only allowed the target
to be followed by `in`, so a following `,` (which continues the index
target list) fell through to the "not a statement level" error. Allow
a comma there as well.

ruby/prism@1f42963317
(ruby/prism#4151)

`ARGUMENT_BLOCK_FORWARDING` seems to have been left unused since ruby/prism@8266572
The other I didn't find (possible I missed it)

ruby/prism@b8f076a61c
enc_list_update makes the frozen encoding list shareable by setting
RUBY_FL_SHAREABLE directly. Use the public RB_OBJ_SET_SHAREABLE() helper
instead, which is the intended way to mark an object shareable
(rb_obj_set_shareable). No behavioural change on the shared interpreter;
it keeps the encoding-list sharing off the raw-flag path.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
rb_io_set_timeout stores the timeout VALUE into the IO's fptr with a plain
assignment, missing the generational write barrier for the old->young
reference. Use RB_OBJ_WRITE.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
When embeddeding `struct re_pattern_buffer`, `RRegexp` end up
488B large, which result in a rather minimal 24B waste in 512B slots.

This however requires a few changes:
  - Stop relying on `RREGEXP_PTR == NULL` to check for initialization.
  - `reg_copy` requires a new `onig_reg_copy_body` API.
Does not know `assume` attribute.
Since Git 2.46, commands like `git commit` spawn a detached
`git maintenance run --auto` process, which briefly creates
`.git/objects/maintenance.lock`. Specs copying a just-committed
repository with FileUtils.cp_r can hit the lock file disappearing
between readdir and lstat, causing flaky Errno::ENOENT failures on
macOS CI runners with newer Git.

https://github.com/ruby/ruby/actions/runs/28764006107/job/85284933867

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@pull pull Bot locked and limited conversation to collaborators Jul 6, 2026
@pull pull Bot added the ⤵️ pull label Jul 6, 2026
@pull pull Bot merged commit d8a2f6c into turkdevops:master Jul 6, 2026
1 of 3 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants