summaryrefslogtreecommitdiff
path: root/spec/bundler/runtime
AgeCommit message (Collapse)Author
2024-10-04[rubygems/rubygems] Remove outdated conditionals from testsSamuel Giddins
Signed-off-by: Samuel Giddins <segiddins@segiddins.me> https://github.com/rubygems/rubygems/commit/06eec6d855
2024-10-02Make spec file for env helpers more genericDavid Rodríguez
2024-10-02[rubygems/rubygems] Fix `bundler/inline` resetting ENVDavid Rodríguez
https://github.com/rubygems/rubygems/commit/72d8d4dbba
2024-10-02[rubygems/rubygems] The `BUNDLER_SETUP` env should also be cleaned upDavid Rodríguez
https://github.com/rubygems/rubygems/commit/47b7e50f64
2024-09-24[rubygems/rubygems] Fix `bundler/inline` overwriting lockfilesDavid Rodríguez
This was introduced by https://github.com/rubygems/rubygems/commit/0b7be7bb7705, because the original patch was not adapted to some recent refactorings. https://github.com/rubygems/rubygems/commit/0bca60d6e5 Co-authored-by: Hiroshi SHIBATA <hsbt@ruby-lang.org>
2024-09-23[rubygems/rubygems] Don't try to auto-install dev versions of Bundler not ↵David Rodríguez
available remotely https://github.com/rubygems/rubygems/commit/1a7a3fdeb9
2024-09-20[rubygems/rubygems] Don't try to install locked bundler when `--local` is passedDavid Rodríguez
https://github.com/rubygems/rubygems/commit/907d46964d
2024-09-17[rubygems/rubygems] Bump rubies in CI to 3.3.5David Rodríguez
A spec needed changes because now loading the default `json` prints a warning about `ostruct` getting loaded although it will be removed in the future. Use a different default gem to test this. https://github.com/rubygems/rubygems/commit/7415a66906 Co-authored-by: Samuel Giddins <segiddins@segiddins.me>
2024-09-11[rubygems/rubygems] Fix `bundle exec rake install` failing when local gem ↵David Rodríguez
has extensions and `gemspec` DSL is being used In a `bundle exec` context, the local specification will actually be part of the known specifications, so RubyGems will assume it has already been installed, which is not actually true. This will cause `RequestSet` to rebuild extensions for a gem that's not actually installed, causing errors. The fix is to make sure detection of installed activation requests considers not only that there's a known spec with the same full name as the one being installed, but also that this spec is installed in the same gem_home were pretend to install the new gem. https://github.com/rubygems/rubygems/commit/a8ef1286a6
2024-09-10[rubygems/rubygems] Mark to exclude examples at ruby/ruby repositoryHiroshi SHIBATA
`make test-bundler` on ruby/ruby don't have installed gemspec. So, `require "psych"` didn't activate psych as default gems on ruby repo. https://github.com/rubygems/rubygems/commit/f8ca514cbb
2024-09-10[rubygems/rubygems] Added example for bundler/inline conflictHiroshi SHIBATA
https://github.com/rubygems/rubygems/commit/6b1e8a14bd
2024-07-23[rubygems/rubygems] Enforce passing a block to `simulate_platform`David Rodríguez
https://github.com/rubygems/rubygems/commit/0658903e25
2024-07-09[rubygems/rubygems] Minor Bundler spec improvementsDavid Rodríguez
While working on something else I noticed: * Usage of uppercased "RUBY" and "JAVA" as platforms, when those don't really exist. * Usage of some test gems with "1.0" as gemspec version and "1.0.0" as actual version. This commit fixes both inconsistencies to make things more expectable. https://github.com/rubygems/rubygems/commit/e3ec32e247
2024-07-09[rubygems/rubygems] Test using latest rubiesDavid Rodríguez
https://github.com/rubygems/rubygems/commit/6d6646b8bc
2024-07-05[rubygems/rubygems] Use preferred add_dependency instead of ↵Jerome Dalbert
add_runtime_dependency https://github.com/rubygems/rubygems/commit/9a08043858
2024-06-28Synchronize Bundler & RubyGems (#11071)David Rodríguez
2024-06-11[rubygems/rubygems] Auto switch to locked bundler version even when using ↵David Rodríguez
binstubs https://github.com/rubygems/rubygems/commit/076aba8b1c
2024-06-06[rubygems/rubygems] Enable one spec on truffleruby that reproduces the ↵David Rodríguez
Pathname problem Recent refactorings in test suite to not load `pathname` for launching Bundler subprocesses make some specs fail due to the warnings Ruby prints when autoloading `pathname` under a namespace. But enabling this spec also reproduces the hard error it produces on truffleruby. https://github.com/rubygems/rubygems/commit/e47cd78081
2024-06-06[rubygems/rubygems] The `tmp` test helper already joins internallyDavid Rodriguez
https://github.com/rubygems/rubygems/commit/2d9eeadb62
2024-05-29[rubygems/rubygems] Improve default gem handling by treating default gems as ↵David Rodríguez
any other gem For backwards compatibility, make sure default gems are still used as a last resort when materializing, in case no remote, cached, or installed specs are found. https://github.com/rubygems/rubygems/commit/93788f689f
2024-05-24[rubygems/rubygems] Fix performance regression on applications with a local ↵David Rodríguez
cache Even if all gems are properly installed and no resolve is needed, we recently started always reading all packages in `vendor/cache` and extracting specifications from them. This commit fixes the problem by longer making considering cached specs the default and only enable them when a resolve is actually needed. https://github.com/rubygems/rubygems/commit/edeb2c42bf
2024-04-29[rubygems/rubygems] Fix circular require warningDavid Rodríguez
https://github.com/rubygems/rubygems/commit/241d0aafcd
2024-04-25[rubygems/rubygems] Add auto_install support to require "bundler/setup"Josh Nichols
We have some places that already use `bundle config auto_install true`, ie: https://github.com/technicalpickles/rubygems/blob/7a144f3374f6a400cc9832f072dc1fc0bca8c724/bundler/lib/bundler/cli.rb#L11 This applies the same logic (copy and pasted) to happen when you `require "bundler/setup"`. https://github.com/rubygems/rubygems/commit/bb3c922341
2024-04-25[rubygems/rubygems] Don't upcase Windows ENV when backing it upDavid Rodriguez
I apparently did that to fix some issue with case insensitivity but I didn't add a spec, and I think not upcasing should not cause issues. https://github.com/rubygems/rubygems/commit/1b6f23275a
2024-02-16[rubygems/rubygems] bin/rubocop -aHiroshi SHIBATA
https://github.com/rubygems/rubygems/commit/f79a6a004d
2024-02-15Update the error message format in bundlerYusuke Endoh
2024-01-29[rubygems/rubygems] Add a spec to prove uri is no longer loadedDavid Rodríguez
https://github.com/rubygems/rubygems/commit/3a262f55c8
2024-01-29[rubygems/rubygems] Remove no longer needed uri install during specsDavid Rodríguez
https://github.com/rubygems/rubygems/commit/7f35dc19c5
2023-12-16[rubygems/rubygems] Fix Bundler daily CIDavid Rodríguez
A default Bundler copy with vendored net-http is causing a Bundler spec to end up loading that copy instead of the copy of Bundler under test. This is because of vcr, but we don't really need vcr in the command that's failing, so I avoided loading it. https://github.com/rubygems/rubygems/commit/304ab6e1b9
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] 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] Add a spec to cover what vendoring timeout fixesDavid Rodríguez
https://github.com/rubygems/rubygems/commit/2662e45d75
2023-12-13[rubygems/rubygems] Remove no longer needed gem install during testDavid Rodríguez
https://github.com/rubygems/rubygems/commit/bdb78d8289
2023-12-13[rubygems/rubygems] Avoid loading artifice when not necessaryDavid Rodríguez
https://github.com/rubygems/rubygems/commit/ef97ad37bd
2023-12-12Sync with upstream rubygems (#9206)David Rodríguez
2023-12-12[rubygems/rubygems] Bump rake version used by testsDavid Rodríguez
And make it easier to update next time. https://github.com/rubygems/rubygems/commit/1ea4bfa5d8
2023-12-07[rubygems/rubygems] Use modern hashes consistentlyDavid Rodríguez
https://github.com/rubygems/rubygems/commit/bb66253f2c
2023-12-05[rubygems/rubygems] Converts Bundler lockfile checksum validation to opt-in onlyMartin Emde
Looks for the CHECKSUMS section in the lockfile, activating the feature only if the section exists. Without a CHECKSUMS section, Bundler will continue as normal, validating checksums when gems are installed while checksums from the compact index are present. https://github.com/rubygems/rubygems/commit/2353cc93a4
2023-11-27[rubygems/rubygems] Remove no longer necessary workaround for old RubyGemsDavid Rodríguez
https://github.com/rubygems/rubygems/commit/ed4eaefac0
2023-11-13[rubygems/rubygems] Make sure to `require "rubygems"` explicitlyNobuyoshi Nakada
This is also done in bundler/lib/bundler/rubygems_integration.rb, but bundler/lib/bundler.rb loads this file before it. https://github.com/rubygems/rubygems/commit/8840d8507b
2023-11-13[rubygems/rubygems] Drop support for Ruby 2.6 and Ruby 2.7 in BundlerDavid Rodríguez
https://github.com/rubygems/rubygems/commit/93619c97ff
2023-10-23[rubygems/rubygems] Use the server checksum, then calculate from gem on disk ↵Mercedes Bernard
if possible 1. Use the checksum provided by the server if provided: provides security knowing if the gem you downloaded matches the gem on the server 2. Calculate the checksum from the gem on disk: provides security knowing if the gem has changed between installs 3. In some cases, neither is possible in which case we don't put anything in the checksum and we maintain functionality as it is today Add the checksums to specs in the index if we already have them Prior to checksums, we didn't lose any information when overwriting specs in the index with stubs. But now when we overwrite EndpointSpecifications or RemoteSpecifications with more generic specs, we could lose checksum info. This manually sets checksum info so we keep it in the index. https://github.com/rubygems/rubygems/commit/de00a4f153
2023-10-23[rubygems/rubygems] Add CHECKSUMS for each gem in lockfileThong Kuah
We lock the checksum for each resolved spec under a new CHECKSUMS section in the lockfile. If the locked spec does not resolve for the local platform, we preserve the locked checksum, similar to how we preserve specs. Checksum locking only makes sense on install. The compact index information is only available then. https://github.com/rubygems/rubygems/commit/bde37ca6bf
2023-10-13Removed examples for warning bundled gemsHiroshi SHIBATA
2023-10-09[rubygems/rubygems] Exempt default gem 'etc' in setup tests for rubies ↵Martin Emde
before 3.2 on windows https://github.com/rubygems/rubygems/commit/834ae8a29a
2023-10-03[rubygems/rubygems] 🚨 Rubocop LintingPeter Boling
https://github.com/rubygems/rubygems/commit/2851e051c3
2023-09-21[rubygems/rubygems] Stop bundler eagerly loading all specs with extsSamuel Giddins
We were setting the wrong `extension_dir` for git specs stubs Additionally, the call to `self.extension_dir` was loading the remote spec, which was avoidable since the stub had an extension dir (and in fact its #gem_build_complete_path does exactly what we want anyway) Finally, now set the base_dir when loading the remote_spec from a stub specification, since the git source sets the base dir for stubs based on where the spec _will_ be installed to, and we want to preserve that so the base_dir for the loaded spec & the stub are the same https://github.com/rubygems/rubygems/commit/a94acb465b
2023-09-01[rubygems/rubygems] Use assertion message strictlyHiroshi SHIBATA
https://github.com/rubygems/rubygems/commit/98da5b9826
2023-08-28[rubygems/rubygems] Fixed malformed lockfile version on installingImir Kiyamov
https://github.com/rubygems/rubygems/commit/c969a192bf
2023-07-30[rubygems/rubygems] Use the dedicated method to convert file pathNobuyoshi Nakada
The dedicated method `File.path` to deal with pathname-like objects has been provided since ruby 1.9.0. Also adds a test for rubygems/rubygems#6837. https://github.com/rubygems/rubygems/commit/258c6eda80
generated by cgit v1.2.3 (git 2.25.1) at 2026-01-19 07:52:49 +0000