ruby.git/test/rubygems/test_gem_specification.rb, branch v3_3_11

Merge RubyGems-3.5.22 and Bundler-2.5.22

2024-10-17T15:55:01+00:00

Merge RubyGems-3.5.21 and Bundler-2.5.21

2024-10-17T15:55:01+00:00

Merge RubyGems-3.5.19 and Bundler-2.5.19

2024-09-25T17:56:17+00:00

Update RubyGems 3.5.16 and Bundler 2.5.16 for Ruby 3.3 (#11252)

2024-07-30T16:05:54+00:00

* Merge RubyGems-3.5.12 and Bundler-2.5.12

* Merge RubyGems-3.5.13 and Bundler-2.5.13

* Merge RubyGems-3.5.14 and Bundler-2.5.14

* Merge RubyGems-3.5.15 and Bundler-2.5.15

* Merge RubyGems-3.5.16 and Bundler-2.5.16

Merge RubyGems 3.5.11 and Bundler 2.5.11 for Ruby 3.3 (#10870)

2024-06-05T04:36:46+00:00

Co-authored-by: Nobuyoshi Nakada

Merge RubyGems 3.5.9 and Bundler 2.5.9 (Fixed CI at Ruby 3.3) (#10348)

2024-04-16T02:22:22+00:00

* Merge RubyGems-3.5.6 and Bundler-2.5.6

* Merge RubyGems-3.5.7 and Bundler-2.5.7

* Merge RubyGems-3.5.8 and Bundler-2.5.8

* Partly reverted about https://github.com/rubygems/rubygems/pull/7483

* Merge RubyGems-3.5.9 and Bundler-2.5.9

Merge RubyGems-3.5.2 and Bundler-2.5.2

2023-12-21T22:24:04+00:00

[rubygems/rubygems] Warn for duplicate meta data links

2023-12-14T00:06:05+00:00

Match order of METADATA_LINK_KEYS to order used by rubygems.org in Links model.
Add missing download_uri key.

https://github.com/rubygems/rubygems/commit/d2922cd6e9

[rubygems/rubygems] Remove non-transparent requirement added to prerelease gems

2023-12-12T01:04:57+00:00

I think we can safely assume these days that all RubyGems and Bundler
versions that will ever bundle a new gem created in 2023 support
prereleases.

So this non transparent requirement is not necessary.

In my opinion, it should be the gem author to explicitly add this
constraint, not RubyGems.

https://github.com/rubygems/rubygems/commit/b165e6d725

[rubygems/rubygems] Drop support for Ruby 2.6 and Ruby 2.7 in RubyGems

2023-11-13T02:06:10+00:00

https://github.com/rubygems/rubygems/commit/10c26a483d