aboutsummaryrefslogtreecommitdiffstats
path: root/lib/bundler
Commit message (Collapse)AuthorAgeFilesLines
* Track Bundler master(2.3.0.dev) branch at ↵Hiroshi SHIBATA2021-01-0441-74/+3260
| | | | 55634a8af18a52df86c4275d70fa1179118bcc20
* Merge RubyGems 3.2.3 and Bundler 2.2.3Hiroshi SHIBATA2020-12-2310-93/+120
|
* Merge RubyGems 3.2.2 and Bundler 2.2.2Hiroshi SHIBATA2020-12-183-6/+17
|
* Prepare to release rubygems-3.2.1 and bundler-2.2.1Hiroshi SHIBATA2020-12-1511-61/+63
|
* Merge prepare version of Bundler 2.2.0Hiroshi SHIBATA2020-12-0862-135/+3064
|
* Merge bundler-2.2.0.rc.2Hiroshi SHIBATA2020-10-1579-227/+352
|
* [rubygems/rubygems] Move comment below shebang in bin/console templateSteven Peckins2020-09-281-2/+1
| | | | | | | | | | In an executable script, the shebang line should be the first line (the file needs to start with the bytes 0x23 0x21). Putting a comment above it will break the script. (Regression test included per @deivid-rodriguez) https://github.com/rubygems/rubygems/commit/962e669feb
* [rubygems/rubygems] Fix ls-files matching regexpNobuyoshi Nakada2020-09-281-2/+2
| | | | | | | | As splitting by NUL means to allow the file names to contain newlines, path names should match at beginning-of-string instead of beginning-of-line. https://github.com/rubygems/rubygems/commit/8a81183236
* bump Bundler's version to 2.2.0.rc.1Hiroshi SHIBATA2020-09-231-1/+1
|
* Fix typos [ci skip]Kazuhiro NISHIYAMA2020-09-171-1/+1
| | | | s/overriden/overridden/
* [rubygems/rubygems] Remove now unneeded codeDavid Rodríguez2020-07-311-7/+0
| | | | | | We patch `net-http-persistent` to not autoload `openssl`. https://github.com/rubygems/rubygems/commit/757dec3cf2
* Import remaining changesDavid Rodríguez2020-07-156-14/+13
| | | | | The "sync with commits" scripts failed to properly import these for some reason.
* [rubygems/rubygems] Unswallow `Gem::Package::FormatError`David Rodríguez2020-07-151-2/+0
| | | | | | | | This error happen in a CI run, and as it is currently, it doesn't give any useful information about the underlying cause. Let's not swallow the original error. https://github.com/rubygems/rubygems/commit/8c17ba2f45
* [rubygems/rubygems] Allow setting a tag prefix to be used by gem release tasksDavid Rodríguez2020-07-151-1/+8
| | | | https://github.com/rubygems/rubygems/commit/679008f23a
* [rubygems/rubygems] Fix line spacing to make Layout/EmptyLines happyUtkarsh Gupta2020-07-151-2/+3
| | | | | | | | | | | | | The Gemfile wasn't properly put in the last commit. As a result, Layout/EmptyLines inspected an offense in the Gemfile. This also fixes the spec w.r.t change in the task default. Signed-off-by: Utkarsh Gupta <utkarsh@debian.org> https://github.com/rubygems/rubygems/commit/d1418fddd3
* [rubygems/rubygems] Add blank lines to make Bundler/OrderedGems happyUtkarsh Gupta2020-07-151-0/+2
| | | | | | | | | | | If the blank lines aren't used, then rubocop tries to sort them in alphabetical order within their section. Thus, adding lines so rubocop considers them as different sections and doesn't try to sort them. Signed-off-by: Utkarsh Gupta <utkarsh@debian.org> https://github.com/rubygems/rubygems/commit/cf44b18f0f
* [rubygems/rubygems] Fix Rakefile to make Style/SymbolArray happyUtkarsh Gupta2020-07-151-1/+5
| | | | | | | | | | | | | In case of multiple Rake tasks, the default tasks would look something like this: `task default: [:spec, :rubocop]` Instead, they should use %i and look something like this: `task default: %i[spec rubocop]` Signed-off-by: Utkarsh Gupta <utkarsh@debian.org> https://github.com/rubygems/rubygems/commit/487ecd59ce
* [rubygems/rubygems] Fix remaining RuboCop issuesUtkarsh Gupta2020-07-155-0/+10
| | | | | | | | | | | | | With #3731 and #3740 merged, this covers up the remaining part of the issues. This was discovered when one tries to create a gem with a different framework. Could be reproduced with: `bundle gem foo --ext --test=test-unit` Signed-off-by: Utkarsh Gupta <utkarsh@debian.org> https://github.com/rubygems/rubygems/commit/51b6457150
* [rubygems/rubygems] Avoid calling LoadError#message because of its slownessJean Boussier2020-07-151-12/+2
| | | | | | Instead we can rely on `LoadError#path` https://github.com/rubygems/rubygems/commit/16d5c3b43c
* [rubygems/rubygems] Constrain (shipped) RuboCop's versionUtkarsh Gupta2020-07-151-1/+1
| | | | | | | | | | | | | | | Right now, we're not specifying the version constraints on RuboCop that is shipped when a new gem is created. This can break specs which runs rubocop on a new skeleton gem as the newer versions of RuboCop are released. This commit ensures that the specs don't break by constraining the RuboCop version. Signed-off-by: Utkarsh Gupta <utkarsh@debian.org> https://github.com/rubygems/rubygems/commit/0b47243edd
* [rubygems/rubygems] Lock rubocop version to 0.80.1Utkarsh Gupta2020-07-151-0/+3
| | | | | | | | | | | | | | | The later RuboCop versions don't work with ruby2.3 so we should lock the version to what works with ruby2.3 as we haven't dropped the support yet. And since we're using the older version of rubocop, also fix `Max` value of `LineLength` to 120, which is the current standard. Without this, rubocop will throw the line length offenses. Signed-off-by: Utkarsh Gupta <utkarsh@debian.org> https://github.com/rubygems/rubygems/commit/46d0a800a2
* [rubygems/rubygems] Make Style/HashSyntax cop happyUtkarsh Gupta2020-07-151-1/+1
| | | | | | | | | | Previously, we were using the old syntax like: `task :default => :spec`, but now this commit uses the new Ruby 1.9 hash syntax. Signed-off-by: Utkarsh Gupta <utkarsh@debian.org> https://github.com/rubygems/rubygems/commit/b41d0fdb56
* [rubygems/rubygems] Roll back to Dir.chdir blockUtkarsh Gupta2020-07-151-1/+3
| | | | | | | | | since without that, evaluating the gemspec from outside `File.expand_path( __dir__)` won't work. Signed-off-by: Utkarsh Gupta <utkarsh@debian.org> https://github.com/rubygems/rubygems/commit/9e5e52a1d9
* [rubygems/rubygems] Fix RuboCop offensesUtkarsh Gupta2020-07-158-6/+20
| | | | | | | | | | | | | These offenses appear when you create a gem with `bundle gem foo` and run `rubocop` over it. Initially, there were around 45 offenses detected, but with #3731 and this, the number of offenses have been reduced to 2. Signed-off-by: Utkarsh Gupta <utkarsh@debian.org> https://github.com/rubygems/rubygems/commit/fe9dcaa1b4
* [rubygems/rubygems] bundler/lib/bundler/installer.rb - fix Windows ↵MSP-Greg2020-07-151-12/+23
| | | | | | | | 'executable_stubs' Windows normal shell requires binstubs with *.cmd extensions https://github.com/rubygems/rubygems/commit/b46326eb1f
* [rubygems/rubygems] Disable parallel installation by default on WindowsDavid Rodríguez2020-06-181-1/+8
| | | | | | | | | | | | | | Since we enabled parallel installation by default, we've fixed all the issues related to it that have come up, except for a Windows issue that we haven't yet figured out. This issue is hit by our specs on a daily basis and there's no reason to believe that it won't be hit by end users in a similar way. So, both to stop the testing flakyness and to prevent regressions in the default behavior on Windows, I'd rather leave the default as it was before on Windows for now. https://github.com/rubygems/rubygems/commit/5d8ab57131
* [rubygems/rubygems] Remove unused methodDavid Rodríguez2020-06-181-6/+0
| | | | https://github.com/rubygems/rubygems/commit/b1b39b8c06
* [rubygems/rubygems] Only add .rubocop.yml when --rubocop flag is passedUtkarsh Gupta2020-06-181-1/+0
| | | | | | Signed-off-by: Utkarsh Gupta <utkarsh@debian.org> https://github.com/rubygems/rubygems/commit/ef2dae4222
* Ship default .rubocop.ymlUtkarsh Gupta2020-06-182-0/+8
| | | | | | | | | | | Currently, there is no `.rubocop.yml` shipped by default. So when a user runs `rubocop` after creating a new gem via `bundle gem foo`, it throws a bunch of offenses. With the default `.rubocop.yml` present, the number of those offenses significantly reduce by 25. Signed-off-by: Utkarsh Gupta <utkarsh@debian.org>
* [rubygems/rubygems] Only add .rubocop.yml when --rubocop flag is passedUtkarsh Gupta2020-06-181-0/+1
| | | | | | Signed-off-by: Utkarsh Gupta <utkarsh@debian.org> https://github.com/rubygems/rubygems/commit/ef2dae4222
* Rename hidden templatesDavid Rodríguez2020-06-185-4/+4
| | | | | | | Because they don't play nice with ruby-core's gitignore and cause issues with ruby-core integration. Also, because it's consistent with other templates such as `gitignore.tt`.
* Undeprecate the `--no-cache` flagDavid Rodríguez2020-06-181-1/+1
| | | | | This is not a remembered option, so it shouldn't have been deprecated. At least not for that reason.
* Removed the old file with https://github.com/rubygems/rubygems/pull/3667Hiroshi SHIBATA2020-06-181-6/+0
|
* Generalize CI templatesFrank Lam2020-06-183-5/+5
|
* Use consistent filenaming for Travis templateFrank Lam2020-06-182-1/+7
|
* Update github workflow templateFrank Lam2020-06-181-3/+3
| | | | * https://github.com/ruby/setup-ruby is now the more recommended action
* Update CI templatesFrank Lam2020-06-182-4/+4
| | | | | * Next version of Bundler will auto choose jobs by default * --retry 3 is already default
* [rubygems/rubygems] Fix nonexistent constant in CircleCI templateFrank Lam2020-06-181-1/+1
| | | | | Co-authored-by: David Rodríguez <deivid.rodriguez@riseup.net> https://github.com/rubygems/rubygems/commit/851f8afad1
* [rubygems/rubygems] Move already configured --test hint to before test file ↵Frank Lam2020-06-181-6/+4
| | | | | | creation https://github.com/rubygems/rubygems/commit/9e5f7a9099
* [rubygems/rubygems] Move already configured --ci hint to before CI file creationFrank Lam2020-06-181-6/+4
| | | | https://github.com/rubygems/rubygems/commit/2af2abe5fd
* [rubygems/rubygems] Lower verboseness of user-facing text for bundle gemFrank Lam2020-06-181-7/+4
| | | | https://github.com/rubygems/rubygems/commit/288f073c3c
* [rubygems/rubygems] Make test framework/CI configuration for bundle gem ↵Frank Lam2020-06-182-11/+21
| | | | | | | | consistent * Add hints for --ci option https://github.com/rubygems/rubygems/commit/5f779f45b0
* [rubygems/rubygems] Remove extra whitespaceFrank Lam2020-06-181-1/+1
| | | | https://github.com/rubygems/rubygems/commit/9986cd01fc
* [rubygems/rubygems] Incorporate naming/grammar suggestions from olleolleolleFrank Lam2020-06-182-5/+5
| | | | https://github.com/rubygems/rubygems/commit/80571452ca
* [rubygems/rubygems] minor language tweaks, small code refactorAndre Arko2020-06-181-27/+20
| | | | https://github.com/rubygems/rubygems/commit/84e9f3711c
* [rubygems/rubygems] update question textColby Swandale2020-06-181-1/+1
| | | | https://github.com/rubygems/rubygems/commit/f14c8a5ec2
* Manually cherry-picked at ↵Hiroshi SHIBATA2020-06-185-2/+89
| | | | https://github.com/rubygems/rubygems/commit/80260b3496e357bf96ffe6f381e29bf25b6749cb
* [rubygems/rubygems] Fix `only_update_to_newer_versions` regressionDavid Rodríguez2020-06-181-1/+2
| | | | | | | | | | | | | | | | | | The `only_update_to_newer_versions` feature flag will enable some new behaviour in bundler 3 (or maybe earlier if we decide to consider it a bug fix) that prevents `bundle update` from unexpectedly downgrading direct dependencies. This seems reasonable, but the current implementation is adding additional requirements for all locked dependencies, not only from the ones in the `Gemfile`. That causes some situations where the `Gemfile` is edited and will resolve to older versions to start failing. This commit fixes the problem by making sure extra requirements are added exclusively for direct dependencies in the `Gemfile`, not for all direct dependencies in the lock file. https://github.com/rubygems/rubygems/commit/128b4596e1
* [rubygems/rubygems] Remove multiline gem specifications correctlyCarsten Wirth2020-06-051-2/+13
| | | | https://github.com/rubygems/rubygems/commit/8dca0ad56e
* [rubygems/rubygems] Fix typoDavid Rodríguez2020-06-051-1/+1
| | | | | | Co-authored-by: Carsten Wirth <carsten.wirth@homeday.de> https://github.com/rubygems/rubygems/commit/c7c5ca68db
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-29 17:34:30 +0000