aboutsummaryrefslogtreecommitdiffstats
path: root/spec/bundler
Commit message (Collapse)AuthorAgeFilesLines
...
* [rubygems/rubygems] Test the actual checksums of the mock gemsNobuyoshi Nakada2022-01-041-0/+7
| | | | https://github.com/rubygems/rubygems/commit/2b42630959
* [rubygems/rubygems] Fix the test to use the mock gem pathNobuyoshi Nakada2022-01-041-3/+5
| | | | | | | "NUL.*" means the NUL device on Windows, as well as mere "NUL", and no data is read. https://github.com/rubygems/rubygems/commit/e2c7d22745
* [rubygems/rubygems] Append a newline to the checksum fileNobuyoshi Nakada2022-01-041-1/+1
| | | | https://github.com/rubygems/rubygems/commit/48ea2778e9
* [rubygems/rubygems] Fix checksumNobuyoshi Nakada2022-01-041-0/+6
| | | | | | | Calculate the checksum of the content, not the given pathname at the build time itself. https://github.com/rubygems/rubygems/commit/b60ee97ee9
* [rubygems/rubygems] Better way to join path componentsDavid Rodríguez2021-12-301-1/+1
| | | | | | | The current way works, but error messages show duplicate "/" in paths, which is weird. https://github.com/rubygems/rubygems/commit/9123deb4fa
* [rubygems/rubygems] Fix `bundle update --bundler` no longer updating lockfileDavid Rodríguez2021-12-281-0/+35
| | | | https://github.com/rubygems/rubygems/commit/a053b7e4d4
* [rubygems/rubygems] Run `bundle install` in verbose modeDavid Rodríguez2021-12-271-1/+1
| | | | | | To see if we get more information when this fails. https://github.com/rubygems/rubygems/commit/853d33fdc3
* Track RubyGems 3.4.0dev and Bundler 2.4.0devHiroshi SHIBATA2021-12-275-62/+64
|
* [rubygems/rubygems] Don't add verbose flag so opaquely for realworld specsDavid Rodríguez2021-12-271-1/+0
| | | | https://github.com/rubygems/rubygems/commit/fa8455ef7c
* [rubygems/rubygems] Move setup to the spec that uses itDavid Rodríguez2021-12-271-9/+11
| | | | https://github.com/rubygems/rubygems/commit/7cf0a8fa8e
* [rubygems/rubygems] Remove unused includeDavid Rodríguez2021-12-271-2/+0
| | | | https://github.com/rubygems/rubygems/commit/a581a1dd50
* [rubygems/rubygems] Remove the rest of the `RUBY_VERSION` monkeypatchingDavid Rodríguez2021-12-272-18/+23
| | | | | | | Since we're at it. This generates a bunch of warnings and seems like a brittle way to test things, so let's get rid of it. https://github.com/rubygems/rubygems/commit/f5d45520e0
* [rubygems/rubygems] Update some specs to pass ruby-head CIDavid Rodríguez2021-12-272-34/+44
| | | | | | | | | | | | | | | These specs were monkeypatching `RUBY_VERSION`, but that obviously doesn't change the running ruby to behave any different. The removal of some features, in particular, `String#untaint`, made these specs fail, because untaint is no longer available under ruby-core and bundler calls `untaint` when `RUBY_VERSION` is less than "2.7", which these specs were overwriting it to be. Rewrite these specs to not overwrite `RUBY_VERSION`, but still test the same things. https://github.com/rubygems/rubygems/commit/e8c7b92901
* Merge RubyGems-3.3.3 and Bundler-2.3.3Hiroshi SHIBATA2021-12-251-0/+23
|
* Merge RubyGems-3.3.2 and Bundler-2.3.2Hiroshi SHIBATA2021-12-241-5/+2
|
* Merge RubyGems-3.3.1 and Bundler-2.3.1Hiroshi SHIBATA2021-12-2311-36/+30
|
* Reverts the accidental commits for rubygems/bundler.Hiroshi SHIBATA2021-12-221-22/+2
| | | | | | | | We stay to the stable version for releasing Ruby 3.1.0. Revert commits: b86a7ba49252e00e19c22bbcdc821b5acc31ff92 ef973aa7aa65143a4f05d623c016d459426770d0
* [rubygems/rubygems] Fix error when gem specified twice in gemfile under ↵David Rodríguez2021-12-221-0/+16
| | | | | | different platforms https://github.com/rubygems/rubygems/commit/83bc87ca98
* [rubygems/rubygems] These commands shouldn't be failing, just warningDavid Rodríguez2021-12-221-2/+6
| | | | https://github.com/rubygems/rubygems/commit/04b1ac72b9
* Merge RubyGems-3.3.0 and Bundler-2.3.0Hiroshi SHIBATA2021-12-219-125/+163
|
* [rubygems/rubygems] Print warning when running potentially problematic ↵David Rodríguez2021-12-211-0/+1
| | | | | | | | rubygems + ruby combinations https://github.com/rubygems/rubygems/commit/d6df0b7de0 Co-authored-by: André Arko <andre@arko.net>
* [rubygems/rubygems] Rename `BUNDLE_SPEC_RUN` environment variableDavid Rodríguez2021-12-212-9/+9
| | | | | | | | The `BUNDLE_` prefix should be reserved to first class settings that should be listed when running `bundle config`. This one is just a hacky environment variable that has not corresponding documented setting. https://github.com/rubygems/rubygems/commit/7e255c5058
* [rubygems/rubygems] Error tracing should be printed to stderrDavid Rodríguez2021-12-202-2/+6
| | | | https://github.com/rubygems/rubygems/commit/23178f7d7b
* [rubygems/rubygems] Improve errors a bit moreDavid Rodríguez2021-12-173-9/+24
| | | | https://github.com/rubygems/rubygems/commit/f481e8f41a
* [rubygems/rubygems] Share gem not found logic with transitive dependencies tooDavid Rodríguez2021-12-171-0/+21
| | | | https://github.com/rubygems/rubygems/commit/e4a1a9663d
* [rubygems/rubygems] Fix crash when no matching variants are found for the ↵David Rodríguez2021-12-171-0/+20
| | | | | | | | | | current platform If we are resolving a dependency against a particular platform, and there are no platform specific variants of the candidates that match that platform, we should not consider those candidates. https://github.com/rubygems/rubygems/commit/f6077fe27d
* [rubygems/rubygems] Improve resolver error messagesDavid Rodríguez2021-12-172-5/+5
| | | | | | Use a more standard naming for gems. https://github.com/rubygems/rubygems/commit/75121e83f1
* Merge RubyGems and Bundler masterHiroshi SHIBATA2021-12-153-8/+8
| | | | Merge from https://github.com/rubygems/rubygems/commit/793ad95ecb40e84a1dcb4cb60f2686843ed90de5
* [rubygems/rubygems] Add `github` and `ref` options to `bundle add`Vyacheslav Alexeev2021-12-111-2/+35
| | | | https://github.com/rubygems/rubygems/commit/c3e54acab0
* [rubygems/rubygems] Ignore dependencies not actually locked from frozen checkDavid Rodríguez2021-12-101-0/+11
| | | | | | Only needed if there can be no explicit global source (bundler < 3). https://github.com/rubygems/rubygems/commit/73923f4af5
* [rubygems/rubygems] Cancel deprecation of custom git sourcesDavid Rodríguez2021-12-081-69/+0
| | | | https://github.com/rubygems/rubygems/commit/99cd6e0627
* [rubygems/rubygems] Add require parameter to `bundle add``Simon Fish2021-12-081-0/+12
| | | | | | | | | | | | | | | | Test and ensure "false" is handled Don't use yield_self to operate on autorequire Remove duplicate autorequire Add banner to require option Don't use json to break down require params Pass linter https://github.com/rubygems/rubygems/commit/a4f2f8ac17
* [rubygems/rubygems] Pass "--" to git commands to separate positional and ↵David Rodríguez2021-12-071-4/+24
| | | | | | | | | optional args To make sure git uri's specified in Gemfile are never misinterpreted as optional arguments, potentially allowing for local code execution. https://github.com/rubygems/rubygems/commit/90b1ed8b9f
* [rubygems/rubygems] Don't cleanup paths from gems already activated from ↵David Rodríguez2021-12-071-0/+23
| | | | | | | | | | | | | | | | | | | `$LOAD_PATH` This way, if some default gem has been required before bundler, and rubygems has enhanced the `$LOAD_PATH` to use the latest version in the system, further requires of that default gem after bundler has been activated will use the same version and don't cause redefinition warnings or worse problems derived from the fact of mixing up two different versions. That, unless the gem is a `Gemfile` dependency. In that case, we'll get a mismatch error anyways as we do now. This fix doesn't mean that all default gems internally used by bundler/rubygems are now supported inside `Gemfile`'s. That should be handled case by case, but it will now bite people only when they try to add the gem to their `Gemfile`, not before. https://github.com/rubygems/rubygems/commit/7325530547
* [rubygems/rubygems] Feature: accept pull request URLs as github sourceJean Boussier2021-12-061-0/+39
| | | | | | | | | | | | | | | | | | | | | | | Very often github source is used to temporarily use a modified gem while a PR upstream is being reviewed. So for instance https://github.com/ruby/bigdecimal/pull/211 will look like: ```ruby gem "bigdecimal", github: "casperisfine/bigdecimal", branch: "git-gem" # https://github.com/ruby/bigdecimal/pull/200 ``` It's annoying because you have to fiddle with the branch name, which is copied as `casperisfine:git-gem`, etc etc. If I could simply use the PR URL like this: ``` gem "bigdecimal", github: "https://github.com/ruby/bigdecimal/pull/211" ``` It would make a very common task for me so much simpler. https://github.com/rubygems/rubygems/commit/517c527751
* [rubygems/rubygems] Add --version parameter to bundle info command.Josef Šimánek2021-12-061-0/+5
| | | | https://github.com/rubygems/rubygems/commit/7d9fdd908d
* [rubygems/rubygems] Let original EACCES error be raisedDavid Rodríguez2021-12-041-10/+0
| | | | | | | | | | | | | | This block of code already wraps file operations with `SharedHelpers.filesystem_access`, which rescues and re-raises more friendly errors. Also, I'm not fully sure creating a temporary directory can end up raising an `Errno::EACCES` error from reading `tmpdir` sources. Finally, this rescue block apparently leads to some false positives when firewall is blocking the ruby executable on Windows, or at least that's what we've got reported. In any case, I think it's best to let the original error be raised. https://github.com/rubygems/rubygems/commit/f7dbe54404
* [rubygems/rubygems] Improve source gemfile/lockfile equivalence checksDavid Rodríguez2021-12-031-5/+5
| | | | | | | | | | Since we no longer have multiple global sources, each top level dependency is always pinned to a single source, so it makes little sense to talk about adding or removing a source. Instead, source changes always mean to change the source one or more dependencies are pinned to. This logic can now be much simpler. https://github.com/rubygems/rubygems/commit/f1d33fa0df
* [rubygems/rubygems] Improve sources representationDavid Rodríguez2021-12-032-5/+5
| | | | | | | | | | | | | We have two representations of a source. Once used for sorting, which should not depend on the source's state, but solely on its static information, like remotes. Another one used for error and informational messages, which should properly inform about the exact state of the source when the message is printed. This commit makes the latter be the default implementation of `to_s`, so that error and informational messages are more accurate by default. https://github.com/rubygems/rubygems/commit/b5f2b88957
* [rubygems/rubygems] Don't overwrite locked dependency sources too earlyDavid Rodríguez2021-12-031-1/+1
| | | | | | Otherwise we hide some useful message about dependency source changes. https://github.com/rubygems/rubygems/commit/c926673c5b
* [rubygems/rubygems] Fix incorrect order in changed sources messageDavid Rodríguez2021-12-031-1/+1
| | | | https://github.com/rubygems/rubygems/commit/6f1b5f68de
* [rubygems/rubygems] Fix gemspec source unlocking also for prereleases like ↵David Rodríguez2021-12-021-0/+33
| | | | | | | | | 0.0.0.SNAPSHOT The default prerelease requirement in rubygems doesn't actually match things like "0.0.0.SNAPSHOT". https://github.com/rubygems/rubygems/commit/711498b342
* [rubygems/rubygems] Fix materialization of locked 0 prereleasesDavid Rodríguez2021-12-021-0/+33
| | | | | | | | | | Since the default requirement in rubygems is ">= 0", it was failing to match 0 prereleases. Changing the default globally to be ">= 0.a" instead is a major refactoring that's quite tricky to make backwards compatible, so I'm special casing this where needed for now to fix the regression. https://github.com/rubygems/rubygems/commit/68fe37937c
* Merge rubygems master fd676ac464491afaa0baf5435cb11b3f86229cbdHiroshi SHIBATA2021-12-012-2/+9
|
* Removed vcr files. They are needless for this repoHiroshi SHIBATA2021-12-012-7/+0
|
* [rubygems/rubygems] Fix escape of filenames in `bundle doctor`ooooooo-q2021-11-301-0/+10
| | | | https://github.com/rubygems/rubygems/commit/3ede1435ea
* [rubygems/rubygems] Fix missing locked specs when depended on other platformDavid Rodríguez2021-11-271-0/+43
| | | | https://github.com/rubygems/rubygems/commit/0396e899db
* [rubygems/rubygems] Fix `bundle info` sometimes claiming that bundler has ↵David Rodríguez2021-11-261-0/+8
| | | | | | been deleted https://github.com/rubygems/rubygems/commit/fe1a31db31
* [rubygems/rubygems] Fix bad instance variable nameDavid Rodríguez2021-11-251-1/+1
| | | | | | | Recent changes made a warning while running specs show up for some reason, and it revealed this error. https://github.com/rubygems/rubygems/commit/bbf55de38e
* [rubygems/rubygems] Check not having load system features also for ↵David Rodríguez2021-11-251-9/+3
| | | | | | successful runs https://github.com/rubygems/rubygems/commit/4807bd19a5
generated by cgit v1.2.3 (git 2.39.1) at 2024-09-03 20:24:05 +0000