ruby.git/spec/bundler/install/gemfile, branch master

[ruby/rubygems] Stop blanket-unlocking the lockfile on :all overrides

2026-05-08T06:43:45+00:00

Previously, any :all override called unlock_all_locked_specs_for_override
which pushed every locked spec into @gems_to_unlock. A user adding a
narrow `override :all, required_ruby_version: :ignore_upper` thus paid
for a full re-resolve that could pull unrelated dependency
upgrades/downgrades.

Make :all overrides leave the lockfile alone at converge time. They
take effect on a fresh resolution (no lockfile) or when the user opts
in via `bundle update`. Per-gem overrides retain their unlock for the
named gem since the user explicitly named the target.

https://github.com/ruby/rubygems/commit/3c95ab99e3

Co-Authored-By: Claude Opus 4.7 (1M context)

[ruby/rubygems] Show active overrides when resolution fails

2026-05-08T06:43:44+00:00

Append the list of currently active overrides (with Gemfile location,
when known) to the SolveFailure message so a user investigating a
"could not find compatible versions" error sees what override changed
the constraint set instead of being misled by the resolver-reported
requirement.

https://github.com/ruby/rubygems/commit/10b8b53270

Co-Authored-By: Claude Opus 4.7 (1M context)

[ruby/rubygems] Cover install-time compatibility for metadata overrides

2026-05-08T06:43:43+00:00

Drive bundle install end-to-end with a gem whose required_ruby_version
or required_rubygems_version excludes the current runtime, asserting
that a per-gem override (and an :all override) makes the install
succeed instead of erroring at the install-time compatibility gate.

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

Co-Authored-By: Claude Opus 4.7 (1M context)

[ruby/rubygems] Cover :all target metadata-field override end-to-end

2026-05-08T06:43:42+00:00

Exercise :all required_ruby_version overrides applied to multiple gems
at once, the per-gem precedence rule, and re-resolution against an
existing lockfile when an :all override is introduced.

https://github.com/ruby/rubygems/commit/81f2bfcf9b

Co-Authored-By: Claude Opus 4.7 (1M context)

[ruby/rubygems] Cover required_ruby_version and required_rubygems_version overrides

2026-05-08T06:43:40+00:00

Add integration coverage exercising :ignore_upper and nil overrides
against per-gem metadata fields, transitive propagation, and lockfile
re-resolution when a metadata override is added against an existing
lockfile. The cases drive `bundle lock` so they exercise the resolver
without RubyGems' install-time required_ruby_version gate, which is
addressed in a later step.

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

Co-Authored-By: Claude Opus 4.7 (1M context)

[ruby/rubygems] Assert that override directives never leak into the lockfile

2026-05-08T06:43:38+00:00

Lock the byroot policy decision (overrides are a Gemfile concept and
must not be serialized into Gemfile.lock) with a regression test, so a
future change that starts emitting override metadata in the lock would
fail loudly.

https://github.com/ruby/rubygems/commit/9524b785c5

Co-Authored-By: Claude Opus 4.7 (1M context)

[ruby/rubygems] Mark transitive-only overrides as changed against the lockfile

2026-05-07T09:24:56+00:00

converge_dependencies only iterates @dependencies (Gemfile-declared
direct deps), so an override that targets a gem present only as a
transitive dependency never registered as a change. With an existing
lockfile, @dependency_changes stayed false, the resolver was skipped,
and the override was a silent no-op. After the direct-dep loop,
inspect @overrides for any String target that is locked but not a
direct dep and force it onto @gems_to_unlock / @changed_dependencies
so resolution runs and the Resolver-side override hook applies.

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

Co-Authored-By: Claude Opus 4.7 (1M context)

[ruby/rubygems] Add version: nil integration coverage

2026-05-07T09:24:55+00:00

Verify end-to-end that override(..., version: nil) collapses the
requirement to Gem::Requirement.default for both direct deps (a
Gemfile pin to 0.9.1 is removed) and transitive deps (a
myrack_middleware-imposed = 0.9.1 floor is removed).

https://github.com/ruby/rubygems/commit/7df463f5c7

Co-Authored-By: Claude Opus 4.7 (1M context)

[ruby/rubygems] Add :ignore_upper integration coverage

2026-05-07T09:24:54+00:00

Verify end-to-end that override(..., version: :ignore_upper) drops
< / <= bounds and folds ~> into >= so a Gemfile-pinned 0.9.1 ceiling
no longer prevents myrack 1.0.0 from being chosen.

https://github.com/ruby/rubygems/commit/95224cff50

Co-Authored-By: Claude Opus 4.7 (1M context)

[ruby/rubygems] Cover prerelease pin via override

2026-05-07T09:24:54+00:00

When the Gemfile dependency does not request a prerelease,
Resolver::Package's prerelease policy normally filters them out.
Because Definition#expanded_dependencies now feeds the effective
(override-applied) dep into Resolver::Base, an override that pins an
exact prerelease propagates into the package's prerelease decision
and the prerelease becomes selectable. Lock that contract in with an
integration test on a has_prerelease 1.0 / 1.1.pre fixture.

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

Co-Authored-By: Claude Opus 4.7 (1M context)