ruby.git/lib/rubygems/specification.rb, branch v4.0.2 The Ruby Programming Language Merge RubyGems/Bundler 4.0.5 2026-02-10T01:38:24+00:00 Hiroshi SHIBATA hsbt@ruby-lang.org 2026-02-10T01:07:38+00:00 87b544b8c4400ef2b37405f132846e5c3738213b 






[ruby/rubygems] Undeprecate `Gem::Version.new(nil)`
2025-11-18T04:53:07+00:00

Aaron Patterson
tenderlove@ruby-lang.org

2025-11-16T23:53:00+00:00

5ccaeee2e89310d52d15469719c98d02f103b5aa

It seems like we were trying to deprecate passing `nil` to
Gem::Version.new.  This breaks existing code, and I don't think there is
a good reason to deprecate this usage.

I believe what we want to prevent is the following code:

```ruby
Gem::Specification.new do |spec|
  spec.version = nil
  # suddenly the spec version is 0!
  p spec.version
end
```

This commit allows people to manually construct `Gem::Version.new(nil)`,
but when someone assigns `nil` as the Gem specification version, it sets
the spec version to `nil` (making the specification invalid).  People
who manually construct `Gem::Version` objects and use nil should be
allowed to do it, and `Gem::Version.new(nil) == Gem::Version.new("0")`,
but people who assign `nil` in a gemspec will get an invalid gemspec.

I think deprecation started
[here](https://github.com/ruby/rubygems/pull/2203) but there doesn't
seem to be a reason to do it.

Fixes https://github.com/ruby/rubygems/pull/9052

https://github.com/ruby/rubygems/commit/ded5e909c2





It seems like we were trying to deprecate passing `nil` to
Gem::Version.new.  This breaks existing code, and I don't think there is
a good reason to deprecate this usage.

I believe what we want to prevent is the following code:

```ruby
Gem::Specification.new do |spec|
  spec.version = nil
  # suddenly the spec version is 0!
  p spec.version
end
```

This commit allows people to manually construct `Gem::Version.new(nil)`,
but when someone assigns `nil` as the Gem specification version, it sets
the spec version to `nil` (making the specification invalid).  People
who manually construct `Gem::Version` objects and use nil should be
allowed to do it, and `Gem::Version.new(nil) == Gem::Version.new("0")`,
but people who assign `nil` in a gemspec will get an invalid gemspec.

I think deprecation started
[here](https://github.com/ruby/rubygems/pull/2203) but there doesn't
seem to be a reason to do it.

Fixes https://github.com/ruby/rubygems/pull/9052

https://github.com/ruby/rubygems/commit/ded5e909c2







[ruby/rubygems] Removed deprecated Gem::Specification#has_rdoc, has_rdoc= and has_rdoc?
2025-11-14T07:36:28+00:00

Hiroshi SHIBATA
hsbt@ruby-lang.org

2025-11-14T06:14:33+00:00

6f18898f4902b2717442f9bef4faa876d58f99de

https://github.com/ruby/rubygems/commit/b043538576





https://github.com/ruby/rubygems/commit/b043538576







[ruby/rubygems] bin/rubocop -a --only Layout/EmptyLinesAroundClassBody
2025-11-14T06:09:39+00:00

Hiroshi SHIBATA
hsbt@ruby-lang.org

2025-11-14T04:45:05+00:00

46227126957b154a73ec34068ccb6c40b62981a8

https://github.com/ruby/rubygems/commit/94d4e633d1





https://github.com/ruby/rubygems/commit/94d4e633d1







[ruby/rubygems] Removed deprecated Gem::Specification#validate_metadata, validate_dependencies and validate_permissions
2025-11-14T06:09:38+00:00

Hiroshi SHIBATA
hsbt@ruby-lang.org

2025-11-14T03:01:10+00:00

31928c10a25c8ad14b4e7d7378afa6d83a1ecec0

https://github.com/ruby/rubygems/commit/fbf38fc190





https://github.com/ruby/rubygems/commit/fbf38fc190







[ruby/rubygems] Removed deprecated Gem::Specification#default_executable
2025-11-14T06:09:37+00:00

Hiroshi SHIBATA
hsbt@ruby-lang.org

2025-11-14T01:55:16+00:00

9fd3ab9e4a7157830c425ddf190b455f3ab00871

https://github.com/ruby/rubygems/commit/84ceaff1b7





https://github.com/ruby/rubygems/commit/84ceaff1b7







[rubygems/rubygems] remove some memoization
2025-10-15T02:05:45+00:00

Aaron Patterson
tenderlove@ruby-lang.org

2025-10-15T00:30:52+00:00

8d438678023aa453717954bb519308b5c3eec0fe

I don't think these methods are hotspots, and since gem specifications
are sometimes serialized to yaml / marshal, I think we should remove as
many instance variables as possible

https://github.com/rubygems/rubygems/commit/40490d918b





I don't think these methods are hotspots, and since gem specifications
are sometimes serialized to yaml / marshal, I think we should remove as
many instance variables as possible

https://github.com/rubygems/rubygems/commit/40490d918b







[rubygems/rubygems] Use spaces around optional parameter values
2025-08-18T03:31:51+00:00

David Rodríguez
deivid.rodriguez@riseup.net

2025-08-11T20:02:10+00:00

7125f7635d43f67b1664bf85e72a34d868259822

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





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







[rubygems/rubygems] misc: fix spelling
2025-06-02T22:47:14+00:00

John Bampton
jbampton@gmail.com

2025-05-28T19:30:38+00:00

a763716a9682f367ee664f1f43e36daac9839cbe

https://github.com/rubygems/rubygems/commit/0e40e7d938





https://github.com/rubygems/rubygems/commit/0e40e7d938







[rubygems/rubygems] Sorting files in metadata for reproducibility
2025-04-01T00:55:19+00:00

Giacomo Benedetti
giacomo.bndt@gmail.com

2025-03-14T11:01:53+00:00

fce2c386a5e3a49bf8863c7550e257e349ca093b

https://github.com/rubygems/rubygems/commit/792117980b





https://github.com/rubygems/rubygems/commit/792117980b