ruby.git/spec/bundler/commands/doctor_spec.rb, branch master

[ruby/rubygems] Allow File.writable?/File.readable? fallbacks in doctor specs

2026-05-14T01:37:59+00:00

doctor_spec.rb strict-stubs File.writable? and File.readable? with
specific paths, which was safe as long as the doctor command did
not trigger Plugin.hook. The new before-eval/after-eval hooks
fire during Bundler.definition, which the doctor command calls,
and Plugin.hook initializes Plugin::Index, which touches
Bundler.user_home and calls File.writable? on the test home path.
Those calls do not match the stubs and RSpec raises.

Match the existing File.exist? pattern and add and_call_original
fallbacks so unrelated paths fall through to the real methods,
while the specific stubs continue to control the paths under test.

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

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

Revert "[ruby/rubygems] Move bundler/spec to top-level spec/ directory"

2026-03-23T07:22:35+00:00

This reverts commit d1b8503e59dc5171580efba9f33f256b79008bc4.

[ruby/rubygems] Move bundler/spec to top-level spec/ directory

2026-03-23T07:16:39+00:00

This simplifies running bundler tests from the repository root.
Tests can now be run with `bin/rspec spec/...` instead of needing
to chdir into bundler/ first.

https://github.com/ruby/rubygems/commit/28670c2e20

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

[rubygems/rubygems] Fix doctor command parsing of otool output

2025-05-12T02:09:22+00:00

I have several gem dylibs that have a line matching "(compatibility "
with no file path preceding it.

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

[rubygems/rubygems] Define `bundler doctor` as a subcommand

2025-04-22T02:27:23+00:00

- See explanation in previous commit https://github.com/rubygems/rubygems/commit/170890befb4c

https://github.com/rubygems/rubygems/commit/8f1b5a4479

[rubygems/rubygems] Modify `bundle doctor` to not report issue when files aren't writable:

2025-02-25T06:36:46+00:00

- ### Problem

  Running `bundle doctor` warn about files that aren't writable.
  This makes the output of `bundle doctor` very verbose for something
  I believe isn't really an issue.

  ### Context

  Rubygems keeps the files original permission at the time the gem
  is packaged.
  Many gem maintainers have decided that the permissions of the files
  in their bundled would be 0444, this includes amongst others:
  minitest, selenium, brakeman...

  Any git gems that had a 0444 permissions at some point in its git
  history would also be reported (as bundle doctor look in the
  `cache/bundler/git//object` path).

  While it completely make sense to report when files aren't readable,
  maybe it's worth questioning the usefulness of reporting files
  that can't be written and what problem this causes to the user
  (if any).

  ### Solution

  Removed the check for unwritable file.

  ### Side note

  I also tweaked the "No issues ..." message logic as it was doing
  the opposite (reporting an issue when there is none and vice versa).
  This wasn't caught in tests because as a stub on `Bundler.ui.info`
  was missing.

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

[rubygems/rubygems] Stub-out additional examples and removed needless Error definition

2025-02-13T00:37:50+00:00

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

Expand stub-out scope of Fiddle.dlopen

2025-02-04T22:36:59+00:00

Synchronize Bundler & RubyGems (#11071)

2024-06-28T14:12:29+00:00

[rubygems/rubygems] Update incorrect comments.

2023-10-11T19:07:28+00:00

https://github.com/rubygems/rubygems/commit/6b21f593f3