Skip to content

Accept All すべて承認

Ruby

10 stories

RubyLanguagesRuby 3.3.13 Released Ruby 3.3.13 has been released. This release includes security fixes. Please check the topics below for details.

RubyLanguagesRuby 3.4.12 Released Ruby 3.4.12 has been released. This release includes fixes for bugs in Regexp compilation that GitLab’s CVE-2026-89078, CVE-2026-93577, CVE-2026-97229 and CVE-2026-110264 rely on.

RubyLanguagesRuby 4.0.9 Released Ruby 4.0.9 has been released. This release includes a fix for a bug in Regexp compilation that GitLab’s CVE-2026-110264 relies on. Please see the topic below for details.

RubyLanguagesRegexp compilation fixes related to GitLab's CVE-2026-89078, CVE-2026-93577, CVE-2026-97229 and CVE-2026-110264 We have released Ruby 4.0.9, 3.4.12 and 3.3.13. They fix several bugs in Ruby’s regular expression engine (Onigmo) that GitLab found could be used for remote code execution on GitLab servers.

RubyLanguagesRuby 4.0.8 Released Ruby 4.0.8 has been released. This is a routine update that includes bugfixes. Please see the GitHub releases for further details.

RubyLanguagesRuby 4.1.0-preview1 Released We are pleased to announce the release of Ruby 4.1.0-preview1. Ruby 4.1 introduces Ractor local GC, Windows support of YJIT, autoload_relative, and adds many improvements.

RubyLanguagesRuby 3.4.11 Released Ruby 3.4.11 has been released. This is a regular scheduled update release includes bugfixes. Please see the GitHub releases for further details.

RubyLanguagesRuby 4.0.7 Released Ruby 4.0.7 has been released. This is a routine update that includes bugfixes. Please see the GitHub releases for further details.

RubyLanguagesSecurity advisories: CVE-2026-80212 and CVE-2026-80213 Two vulnerabilities have been discovered in the resolv gem bundled with Ruby. They have been assigned the CVE identifiers CVE-2026-80212 and CVE-2026-80213 . We recommend upgrading the resolv gem.

RubyLanguagesRuby 3.3.12 Released Ruby 3.3.12 has been released. This release includes security fixes. Please check the topics below for details.

On the calendar

予定 · Conferences and launch events, this week's stories from each corner of the industry, and what its press is covering — in English

On view

This week, from that corner the newest stories from the corner of the industry you picked

The wire their own posts, translated

How code moves in 2026 from the industry's own reports

Sources

Fetched every six hours, linked to the original

About

The name is the button.

An agent writes the code now, and a human thumb hovers over Accept all a hundred times a day. The honest question of this decade is what, exactly, you just accepted. So I read the diff.

Eight years as a backend engineer in Stockholm, back in Tokyo since 2023, and I still ship something small most nights, usually badly. My one rule: the only real review of a model is the thing you built with it. That is why there is no leaderboard on this site.

Around a hundred and forty sources come through — the labs' own posts, the papers, the tools, the runtimes and languages nobody is watching yet, the chip under the demo, and the newsletters people actually forward. What is moving gets counted so the week reads at a glance, and every few days I explain one mechanism in plain words.

A story here is a headline, a short excerpt, one image and the link to whoever wrote it. We never reproduce the post; the images belong to their authors. A post written in Japanese appears in Japanese, exactly as it was published, and the link goes to the original.

— Yuki Halvorsen, Tokyo