summaryrefslogtreecommitdiff
path: root/lib/bundler
AgeCommit message (Collapse)Author
2025-10-25[ruby/rubygems] Bump up vendored uri to 0.13.3nagachika
2025-03-24[rubygems/rubygems] Support git 2.49David Rodríguez
One error message that we parse is now slightly different. https://github.com/rubygems/rubygems/commit/758528791d
2024-10-17Merge RubyGems-3.5.22 and Bundler-2.5.22Hiroshi SHIBATA
2024-10-17Merge RubyGems-3.5.21 and Bundler-2.5.21Hiroshi SHIBATA
2024-09-25Merge RubyGems-3.5.20 and Bundler-2.5.20Hiroshi SHIBATA
2024-09-25Merge RubyGems-3.5.19 and Bundler-2.5.19Hiroshi SHIBATA
2024-09-25Merge RubyGems-3.5.18 and Bundler-2.5.18Hiroshi SHIBATA
2024-09-25Merge RubyGems-3.5.17 and Bundler-2.5.17Hiroshi SHIBATA
2024-07-30Update RubyGems 3.5.16 and Bundler 2.5.16 for Ruby 3.3 (#11252)Hiroshi SHIBATA
* Merge RubyGems-3.5.12 and Bundler-2.5.12 * Merge RubyGems-3.5.13 and Bundler-2.5.13 * Merge RubyGems-3.5.14 and Bundler-2.5.14 * Merge RubyGems-3.5.15 and Bundler-2.5.15 * Merge RubyGems-3.5.16 and Bundler-2.5.16
2024-06-04Merge RubyGems 3.5.11 and Bundler 2.5.11 for Ruby 3.3 (#10870)Hiroshi SHIBATA
Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org>
2024-04-16Merge RubyGems 3.5.9 and Bundler 2.5.9 (Fixed CI at Ruby 3.3) (#10348)Hiroshi SHIBATA
* Merge RubyGems-3.5.6 and Bundler-2.5.6 * Merge RubyGems-3.5.7 and Bundler-2.5.7 * Merge RubyGems-3.5.8 and Bundler-2.5.8 * Partly reverted about https://github.com/rubygems/rubygems/pull/7483 * Merge RubyGems-3.5.9 and Bundler-2.5.9
2024-02-05Merge RubyGems 3.5.5 and Bundler 2.5.5 (#9676)Hiroshi SHIBATA
* Merge RubyGems-3.5.4 and Bundler-2.5.4 * Merge RubyGems-3.5.5 and Bundler-2.5.5 * Make tests play with upstream Ruby tests CI broke in https://github.com/ruby/ruby/pull/9604 because if any Ruby tests run `require 'net/http'`, they will pollute the `$LOADED_FEATURES` for the RubyGems tests. We can fix this by renaming the test default gem from `net-http` to `my-http`. See https://github.com/rubygems/rubygems/pull/7379#issuecomment-1901241299 for more details. --------- Co-authored-by: Stan Hu <stanhu@gmail.com>
2023-12-23Merge RubyGems-3.5.3 and Bundler-2.5.3Hiroshi SHIBATA
2023-12-22Merge RubyGems-3.5.2 and Bundler-2.5.2Hiroshi SHIBATA
2023-12-16Pin versions that are RubyGems 2.5.1 and Bundler 2.5.1Hiroshi SHIBATA
2023-12-16Partly pick commit from https://github.com/rubygems/rubygems/pull/7285Samuel Giddins
Refactor vendoring to allow validating vendoring is reproducible Helps ensure that unsuspecting diffs to the vendored code arent accidentally introduced
2023-12-16[rubygems/rubygems] Improve command suggestion when gems are missingDavid Rodríguez
Previous attempt to use a full path when the running version is different than the one that would be activated by default are different was not correct. This is because if this error happens in a `bundle exec` context, the `Gem.loaded_specs` is cleared because we're in an exec'd process, so will be always using a full path in these cases. This alternative approach should do what I was expecting. https://github.com/rubygems/rubygems/commit/e0bb8bf51b
2023-12-16[rubygems/rubygems] Fix Ruby DSL no longer working as expectedDavid Rodríguez
https://github.com/rubygems/rubygems/commit/f6258e5679 Co-authored-by: AndrewSwerlick <andrew.swerlick@gmail.com>
2023-12-15[rubygems/rubygems] Let the guards have some space to breatheMartin Emde
https://github.com/rubygems/rubygems/commit/73f1609715
2023-12-15[rubygems/rubygems] Use a mutex around Checksum::Store @store accessMartin Emde
Not wrapping to_lock since access to it is single threaded and read-only at the time of writing the lockfile. https://github.com/rubygems/rubygems/commit/3b53aa1b12
2023-12-15[rubygems/rubygems] Remove test-only & unused methods from Checksum::StoreMartin Emde
https://github.com/rubygems/rubygems/commit/79636dec12
2023-12-15[rubygems/rubygems] Save array allocation for every dependency in GemfileSamuel Giddins
Only need to check for lack of git key when branch option is present https://github.com/rubygems/rubygems/commit/ebfca1b389
2023-12-15[rubygems/rubygems] Refactor vendoring to allow validating vendoring is ↵Samuel Giddins
reproducible Helps ensure that unsuspecting diffs to the vendored code arent accidentally introduced https://github.com/rubygems/rubygems/commit/7c425d49dd
2023-12-14[rubygems/rubygems] Upgrade vendored librariesDavid Rodríguez
To match the versions that will be included in final ruby release. https://github.com/rubygems/rubygems/commit/84394919fb
2023-12-14[rubygems/rubygems] Improve install advice when some gems are not foundDavid Rodríguez
This problem is quite specific to our dev environment, but I guess the fix could be handy for other situations. After merging a change to treat default gems as regular gems, I get this when trying to run `rubocop` on our repo: ``` $ bin/rubocop --only Performance/RegexpMatch Could not find json-2.6.3 in locally installed gems Run `bundle install --gemfile /Users/deivid/code/rubygems/rubygems/tool/bundler/lint_gems.rb` to install missing gems. ``` However, when running the suggested command, nothing changes and I still get the same error: ``` $ bundle install --gemfile /Users/deivid/code/rubygems/rubygems/tool/bundler/lint_gems.rb Using ast 2.4.2 Using bundler 2.4.10 Using json 2.6.3 Using parallel 1.23.0 Using racc 1.7.1 Using parser 3.2.2.3 Using rainbow 3.1.1 Using regexp_parser 2.8.1 Using rexml 3.2.5 Using rubocop-ast 1.29.0 Using ruby-progressbar 1.13.0 Using unicode-display_width 2.4.2 Using rubocop 1.52.1 Using rubocop-performance 1.14.2 Bundle complete! 2 Gemfile dependencies, 14 gems now installed. Use `bundle info [gemname]` to see where a bundled gem is installed. $ bin/rubocop --only Performance/RegexpMatch Could not find json-2.6.3 in locally installed gems Run `bundle install --gemfile /Users/deivid/code/rubygems/rubygems/tool/bundler/lint_gems.rb` to install missing gems. ``` The problem is that our `bin/rubocop` script uses the development version of Bundler (which has the change causing the problem), but the advice recommands the default version of Bundler, which does not yet have the change. This commit changes the advice to recommend to use the same version of Bundler that run into the problem in the first place. So in the above situation you now get: ``` $ bin/rubocop --only Performance/RegexpMatch Could not find json-2.6.3 in locally installed gems Run `/Users/deivid/code/rubygems/rubygems/bundler/exe/bundle install --gemfile /Users/deivid/code/rubygems/rubygems/tool/bundler/lint_gems.rb` to install missing gems. ``` And running that fixes the problem: ``` $ /Users/deivid//rubygems/rubygems/bundler/exe/bundle install --gemfile /Users/deivid/code/rubygems/rubygems/tool/bundler/lint_gems.rb Fetching gem metadata from https://rubygems.org/......... Fetching json 2.6.3 Installing json 2.6.3 with native extensions Bundle complete! 2 Gemfile dependencies, 14 gems now installed. Use `bundle info [gemname]` to see where a bundled gem is installed. ``` https://github.com/rubygems/rubygems/commit/10a9588c6d
2023-12-14[rubygems/rubygems] Remove extension building sync stuff no longer present ↵David Rodríguez
in RubyGems https://github.com/rubygems/rubygems/commit/59a85388b9
2023-12-14[rubygems/rubygems] RubyGems > 3.2.0.rc.1 is now always providedDavid Rodríguez
https://github.com/rubygems/rubygems/commit/929b521f3a
2023-12-14[rubygems/rubygems] Gem::Specification always has `default_stubs` nowDavid Rodríguez
https://github.com/rubygems/rubygems/commit/30db1eb4a5
2023-12-14[rubygems/rubygems] Remove more methods now defined in all RubyGems versionsDavid Rodríguez
https://github.com/rubygems/rubygems/commit/e015200ffa
2023-12-14[rubygems/rubygems] Remove check only necessary for ancient RubyGemsDavid Rodríguez
https://github.com/rubygems/rubygems/commit/ffa2f03489
2023-12-14[rubygems/rubygems] This patch should be no longer neededDavid Rodríguez
https://github.com/rubygems/rubygems/commit/1139e90931
2023-12-14[rubygems/rubygems] Gem::Specification.find_all_by_name is always defined nowDavid Rodríguez
https://github.com/rubygems/rubygems/commit/1d61c7686b
2023-12-14[rubygems/rubygems] Revert "Improve default gem handling"David Rodríguez
This reverts commit https://github.com/rubygems/rubygems/commit/091b4fcf2b99. https://github.com/rubygems/rubygems/commit/dcade3235f
2023-12-13[rubygems/rubygems] Revert "Merge pull request #7167 from ↵Martin Emde
nevinera/add-json-output-option-to-bundle-outdated" This reverts commit https://github.com/rubygems/rubygems/commit/a4ac5116b8ea, reversing changes made to https://github.com/rubygems/rubygems/commit/8a6b180d0ae5. https://github.com/rubygems/rubygems/commit/a1efe4015d
2023-12-13[rubygems/rubygems] Use match? when regexp match data is unusedSamuel Giddins
Improved performance / reduced allocations https://github.com/rubygems/rubygems/commit/b04726c9a7
2023-12-13[rubygems/rubygems] Store Checksum::Store indexed by spec.lock_nameMartin Emde
https://github.com/rubygems/rubygems/commit/34d6c6c72f
2023-12-13[rubygems/rubygems] Add 3.4 as a supported ruby versionSamuel Giddins
Since ruby trunk will be 3.4 very soon https://github.com/rubygems/rubygems/commit/36dd9a35dc
2023-12-13[rubygems/rubygems] Improve default gem handlingDavid Rodríguez
If a gem is specified in the Gemfile (or resolved as a transitive dependency), it's always resolved from remote/installed sources. Default gems are only used as a fallback for gems not included in the bundle. I believe this leads to more consistent behavior and more portable apps, since all gems will be installed to the configured bundle path, regardless of whether they are default gems or not. https://github.com/rubygems/rubygems/commit/091b4fcf2b
2023-12-13[rubygems/rubygems] Refactor `bundle info`David Rodríguez
https://github.com/rubygems/rubygems/commit/0e919eaa87
2023-12-13[rubygems/rubygems] Remove dead codeDavid Rodríguez
https://github.com/rubygems/rubygems/commit/fad186df39
2023-12-13Normalize bundler bindirDavid Rodríguez
This makes bundler consistent with all other gems, and makes the default installation of Bundler in the release package look like any other bundler installation. Before (on preview3, for example), Bundler executable is installed at: lib/ruby/gems/3.3.0+0/gems/bundler-2.5.0.dev/libexec/bundle Now it's installed in the standard location: lib/ruby/gems/3.3.0+0/gems/bundler-2.5.0.dev/exe/bundle
2023-12-13[rubygems/rubygems] Use vendored timeout from RubyGemsDavid Rodríguez
https://github.com/rubygems/rubygems/commit/cfc5018c54
2023-12-13[rubygems/rubygems] Use vendored net-http in BundlerDavid Rodríguez
https://github.com/rubygems/rubygems/commit/0d758e8926
2023-12-13[rubygems/rubygems] Require `rubygems/request` where it's usedDavid Rodríguez
https://github.com/rubygems/rubygems/commit/73b9498658
2023-12-12Sync with upstream rubygems (#9206)David Rodríguez
2023-12-12[rubygems/rubygems] Make RubyDsl a little easier to read; avoid a Hash sometimesMartin Emde
https://github.com/rubygems/rubygems/commit/2dca83722b
2023-12-12[rubygems/rubygems] Resolve `ruby file: ".ruby-version"` relative to GemfileMartin Emde
https://github.com/rubygems/rubygems/commit/0cbbaed8a5
2023-12-12[rubygems/rubygems] Ensure that the lockfile mtime is not altered on frozen ↵Martin Emde
install https://github.com/rubygems/rubygems/commit/6847709ee0
2023-12-12[rubygems/rubygems] Allow bundle pristine to run in parallelSamuel Giddins
Also fix running when BUNDLE_NO_INSTALL happens to be set, same as with install/update commands https://github.com/rubygems/rubygems/commit/a555fd6ccd
2023-12-12[rubygems/rubygems] Refactor: Wrap filesystem accessFranz Liedke
https://github.com/rubygems/rubygems/commit/119d4bdc09
generated by cgit v1.2.3 (git 2.25.1) at 2026-01-19 18:23:49 +0000