9d6deeba3b (master): Use the X.Y.0 release as the gem-version baseline
1 view
Skip to first unread message
Hiroshi SHIBATA
Apr 17, 2026, 3:36:14 AM (4 days ago) Apr 17
to ruby...@g.ruby-lang.org
Hiroshi SHIBATA 2026-04-17 07:04:49 +0000 (Fri, 17 Apr 2026)
New Revision: 9d6deeba3b
https://github.com/ruby/ruby/commit/9d6deeba3b
Log:
Use the X.Y.0 release as the gem-version baseline
stdgems.org's "X.Y" key tracks the latest 4.0.x patch level, so once a
gem gets bumped in a Ruby patch release the diff baseline shifts forward
and history that should appear in NEWS.md for the next minor disappears.
Prefer the explicit "X.Y.0" key when present so the baseline always
points at the original X.Y.0 release; fall back to "X.Y" or the highest
matching patch otherwise.
Co-Authored-By: Claude Opus 4.7 (1M context) <nor...@anthropic.com>
Modified files:
tool/update-NEWS-github-release.rb
New Revision: 9d6deeba3b
https://github.com/ruby/ruby/commit/9d6deeba3b
Log:
Use the X.Y.0 release as the gem-version baseline
stdgems.org's "X.Y" key tracks the latest 4.0.x patch level, so once a
gem gets bumped in a Ruby patch release the diff baseline shifts forward
and history that should appear in NEWS.md for the next minor disappears.
Prefer the explicit "X.Y.0" key when present so the baseline always
points at the original X.Y.0 release; fall back to "X.Y" or the highest
matching patch otherwise.
Co-Authored-By: Claude Opus 4.7 (1M context) <nor...@anthropic.com>
Modified files:
tool/update-NEWS-github-release.rb
Reply all
Reply to author
Forward
0 new messages