6c5f1225a1 (master): Generate sub-bullets for RubyGems and bundler
0 views
Skip to first unread message
Hiroshi SHIBATA
Apr 17, 2026, 3:36:16 AM (4 days ago) Apr 17
to ruby...@g.ruby-lang.org
Hiroshi SHIBATA 2026-04-17 07:13:49 +0000 (Fri, 17 Apr 2026)
New Revision: 6c5f1225a1
https://github.com/ruby/ruby/commit/6c5f1225a1
Log:
Generate sub-bullets for RubyGems and bundler
RubyGems and bundler were skipped outright in collect_gem_updates, so
NEWS.md never picked up the rubygems/rubygems releases shipped between
the X.Y.0 baseline and the in-development X.(Y+1).0.dev. Wire them
through resolve_repo (RubyGems → rubygems/rubygems, bundler same repo
with a "bundler-" tag prefix) and teach fetch_release_range to filter
and look up tags by that prefix. Display tags strip the prefix so the
rendered diff reads "4.0.3 to v4.0.4, ..." for both gems while the
footnote URLs still point at the actual tag names. When the "to"
version ends in .dev/.beta/.rc/etc., the lookup falls back to the
highest released tag so unreleased dev versions still produce a range
New Revision: 6c5f1225a1
https://github.com/ruby/ruby/commit/6c5f1225a1
Log:
Generate sub-bullets for RubyGems and bundler
RubyGems and bundler were skipped outright in collect_gem_updates, so
NEWS.md never picked up the rubygems/rubygems releases shipped between
the X.Y.0 baseline and the in-development X.(Y+1).0.dev. Wire them
through resolve_repo (RubyGems → rubygems/rubygems, bundler same repo
with a "bundler-" tag prefix) and teach fetch_release_range to filter
and look up tags by that prefix. Display tags strip the prefix so the
rendered diff reads "4.0.3 to v4.0.4, ..." for both gems while the
footnote URLs still point at the actual tag names. When the "to"
version ends in .dev/.beta/.rc/etc., the lookup falls back to the
highest released tag so unreleased dev versions still produce a range
Reply all
Reply to author
Forward
0 new messages