ruby.git/lib/rubygems/specification_policy.rb, branch v4.0.4

Merge RubyGems/Bundler 4.0.5

2026-02-10T01:38:24+00:00

[ruby/rubygems] Remove open-ended and prerelease dependency warnings when building gems

2025-11-04T00:17:49+00:00

In general, rubygems should provide mechanism and not policy.

Pessimistic versioning is not universally better, and in many
cases, it can cause more problems than it solves. Rubygems should
not be warning against open-ended versioning when building gems.
The majority of the default gems with dependencies do not use
pessimistic versioning, which indicates that Ruby itself
recognizes that open-ended versioning is generally better.

In some cases, depending on a prerelease gem is the only choice
other than not releasing a gem. If you are building an extension
gem for a feature in a prerelease version of another gem, then
depending on the prerelease version is the only way to ensure
a compatible dependency is installed.

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

[rubygems/rubygems] Fix spelling, it's "cannot" rather than "can not"

2024-09-17T20:09:07+00:00

https://github.com/rubygems/rubygems/commit/3434f094a2

[rubygems/rubygems] Add Specification#validate_for_resolution

2024-06-25T14:32:19+00:00

This method validates only what is required for resolution, skipping any
irrelevant metadata validation. This will be used by Bundler instead of
doing a full validation, allowing gem authors to use `bundle` commands
immediately in newly created gems without first having to fix invalid
metafata fields in the default gemspec.

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

[rubygems/rubygems] Remove `Gem::Specification#mark_version`

2024-05-03T15:12:55+00:00

This gets in the middle if we ever start allowing to build as if using a
different RubyGems version than the one being run.

This could be useful to make `gem rebuild` a little more usable, and
it's already done by Bundler specs which already make this method a noop
when they need this.

I'm not sure forcefully setting this, even if user explicitly specified
something else is helpful.

Since this could potentially prevent gems explicitly setting a constant
RubyGems version from building, I changed the error of incorrect
RubyGems version from a hard error to a warning, since it will start
happening in those cases if we stop overwriting the version.

https://github.com/rubygems/rubygems/commit/45676af80d

[rubygems/rubygems] Warn on empty or open required_ruby_version specification attribute.

2024-02-27T03:33:45+00:00

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

Vendor uri gem in RubyGems

2024-01-29T03:14:21+00:00

[rubygems/rubygems] Fix rake extension warning

2024-01-24T04:55:42+00:00

https://github.com/rubygems/rubygems/commit/04973e349c

[rubygems/rubygems] bin/rubocop -A --only Style/StringLiteralsInInterpolation

2024-01-11T04:51:52+00:00

https://github.com/rubygems/rubygems/commit/2333f5f9c5

[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