ruby.git/lib/bundler/dependency.rb, branch v4.0.4

Move most of Bundler::GemHelpers to Gem::Platform

2025-06-06T01:22:18+00:00

This will help centralize wheel platform selection logic eventually

Signed-off-by: Samuel Giddins

[rubygems/rubygems] Make Bundler never instantiate development dependencies

2025-02-17T02:04:39+00:00

Bundler does not really have a concept of "development dependencies",
like RubyGems has. Bundler has the more generic concept of "groups".

Under the hood, the `gemspec` DSL will put gemspec development
dependencies under a `:development` Gemfile group, but there's no reason
to instantiate these as development dependencies, they are regular
runtime dependencies, except that they belong in a group named
:development.

By never instantiating development dependencies at all, we avoid having
to introduce hacks to "undo" the type Bundler does not know about, and I
also think the error messages read better.

https://github.com/rubygems/rubygems/commit/9a06fa5bda

[rubygems/rubygems] Make `Bundler::Dependency` more memory efficient

2025-02-06T06:57:55+00:00

When resolving from scratch a Gemfile including only `"gem "rails", "~>
8.0.1"`, I get the following results:

### Before

Total allocated: 288.21 MB (3498515 objects)
Total retained:  119.10 MB (1357976 objects)

### After

Total allocated: 277.44 MB (3383182 objects)
Total retained:  117.55 MB (1338622 objects)

https://github.com/rubygems/rubygems/commit/2d3d6e5015

[rubygems/rubygems] Consolidate the platform into a single list:

2025-01-31T05:34:26+00:00

- Similar change than https://github.com/rubygems/rubygems/commit/29a1be0008e6,
  keep a single source of truth where we store the platform.

  The only change worth highlighing is the platform "maglev".
  It was not part of the supported platform of dependencies,
  so calling `gem 'foo', plaftorm: 'maglev'` would not work.
  However, it was supposed to according to https://github.com/rubygems/rubygems/commit/45ec86e2e528.
  That's why it was possible to do `Bundler.current_ruby.maglev?` or
  `Bundler.current_ruby.maglev_30?`.

  I didn't change the current behaviour and maglev is not supported,
  though I kept the `*maglev` methods as I believe CurrentRuby is
  public API.

https://github.com/rubygems/rubygems/commit/29e219ebcf

[rubygems/rubygems] Consolidated the Ruby version list:

2025-01-31T05:34:25+00:00

- We keep 2 list of supported ruby versions and each time a new ruby
  version is released we need to maintain both list. Forgetting
  to update one would prevent users from adding gem for a specific
  plaftorm (i.e. https://github.com/rubygems/rubygems/commit/7cd19d824d17 and https://github.com/rubygems/rubygems/commit/5462322f8f0c).

  Extracted the list from the Dependency class and moved it to the
  CurrentRuby class (which I believe was originally added for that
  reason).

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

[rubygems/rubygems] Remove unnecessary `@autorequire` initialization

2025-01-28T06:31:53+00:00

It's initialized again later on.

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

Support Ruby 3.5 for bundler platforms

2024-12-25T11:10:18+00:00

[rubygems/rubygems] Enable `Performance/MapCompact` cop

2024-11-26T06:11:05+00:00

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

[rubygems/rubygems] bundler CLI option for add gem --glob=

2024-04-12T13:31:43+00:00

Bundler online documentation says that if the gem is located within a subdirectory of a git repository,
you can use the `:glob` option to specify the location of its .gemspec

`gem 'cf-copilot', git: 'https://github.com/cloudfoundry/copilot', glob: 'sdk/ruby/*.gemspec'`

This change allows for equivalent functionality from the bundler CLI

`bundle add cf-copilot --git=https://github.com/cloudfoundry/copilot --glob=sdk/ruby/*.gemspec`

https://github.com/rubygems/rubygems/commit/91052e5868

Merge RubyGems-3.5.3 and Bundler-2.5.3

2023-12-23T00:34:26+00:00