Issue #21129 has been updated by hsbt (Hiroshi SHIBATA). Assignee set to hsbt (Hiroshi SHIBATA) I'm working this at https://github.com/ruby/ruby/pull/12913 ---------------------------------------- Bug #21129: Backporting strscan fix in Ruby 3.2 https://bugs.ruby-lang.org/issues/21129#change-112270 * Author: andrykonchin (Andrew Konchin) * Status: Closed * Assignee: hsbt (Hiroshi SHIBATA) * ruby -v: 3.2.7 * Backport: 3.1: UNKNOWN, 3.2: REQUIRED, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- An `strscan` version shipped with Ruby 3.2 (`strscan` v3.0.5) has a bug. It was fixed long time ago in `strscan` v3.0.7 (in https://github.com/ruby/strscan/pull/61) but reported recently again in https://github.com/ruby/strscan/issues/132. Ruby 3.2 AFAIK is still normally supported. So does it make sense to have a new Ruby 3.2.x patch level release with `strscan` v3.0.7? -- https://bugs.ruby-lang.org/