bundler 1.12.6 → 1.13.0.pre.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 0c10825a6dd36d796dc657a6f8039afd96a38916
-  data.tar.gz: f217a886e84362517e629c0b21f0df9b2f16d69a
+  metadata.gz: b53f9f6d4261f192e8a29fcd3dde588d2b60f1cb
+  data.tar.gz: c0d3f7377fcd4d3ceaf92c61adcbab5eef1c434d
 SHA512:
-  metadata.gz: bf6f7073d9cbbc8e7b1bf3c4af411f8c5b4e6c858844d8e6af912b92a10f15429ca7bbf2a03873467abbd35030418187c85567da76b558889b85a10e1ae937b4
-  data.tar.gz: 44847eb36667f9634b5874dad78b3bce84f827a6156d27dbc1c2fd5d6203bc1d1ee7dd6ca8a13f8d3f81990c9a38246b6ec19504df737fef4b37cd84e71ed026
+  metadata.gz: 954bf042fe84dce7a3e5bff018761240b3e5ae29da10960afcdf23da4139829b9f19f2d85b152a420bd73edcbe3606b2fef61cf661f7d647c1e7020cff21240b
+  data.tar.gz: 123e6cdb0d99b018add47043dfb45ec83ce78523a2a391eadaab15ba344b94ada9ec02be45b269ca18eb5e4861038b20149b770d21ca2715a20bf56c458a79ab

data/.rubocop_todo.yml

@@ -1,6 +1,6 @@
 # This configuration was generated by
 # `rubocop --auto-gen-config`
-# on 2016-02-09 10:53:24 -0600 using RuboCop version 0.37.1.
+# on 2016-03-29 17:34:30 -0500 using RuboCop version 0.39.0.
 # The point is for the user to remove these configuration records
 # one by one as the offenses are removed from the code base.
 # Note that changes in the inspected code, or installation of new
@@ -52,7 +52,7 @@ Lint/UselessAssignment:
     - 'lib/bundler/index.rb'
     - 'lib/bundler/installer.rb'
 
-# Offense count: 1295
+# Offense count: 1331
 # Configuration parameters: AllowHeredoc, AllowURI, URISchemes.
 # URISchemes: http, https
 Metrics/LineLength:
@@ -63,9 +63,9 @@ Metrics/LineLength:
 Metrics/ParameterLists:
   Max: 6
 
-# Offense count: 52
+# Offense count: 55
 Metrics/PerceivedComplexity:
-  Max: 54
+  Max: 51
 
 # Offense count: 6
 # Cop supports --auto-correct.
@@ -110,26 +110,24 @@ Style/CaseEquality:
 Style/ClassAndModuleChildren:
   Enabled: false
 
-# Offense count: 14
+# Offense count: 11
 # Cop supports --auto-correct.
-# Configuration parameters: SingleLineConditionsOnly.
+# Configuration parameters: EnforcedStyle, SupportedStyles, SingleLineConditionsOnly.
+# SupportedStyles: assign_to_condition, assign_inside_condition
 Style/ConditionalAssignment:
   Exclude:
-    - 'lib/bundler.rb'
     - 'lib/bundler/cli.rb'
     - 'lib/bundler/cli/gem.rb'
     - 'lib/bundler/cli/lock.rb'
-    - 'lib/bundler/cli/outdated.rb'
     - 'lib/bundler/cli/platform.rb'
     - 'lib/bundler/dsl.rb'
     - 'lib/bundler/lazy_specification.rb'
-    - 'lib/bundler/mirror.rb'
     - 'lib/bundler/psyched_yaml.rb'
     - 'lib/bundler/rubygems_integration.rb'
     - 'lib/bundler/source/git.rb'
     - 'lib/bundler/source/rubygems.rb'
 
-# Offense count: 118
+# Offense count: 119
 Style/Documentation:
   Enabled: false
 
@@ -153,6 +151,11 @@ Style/IfInsideElse:
   Exclude:
     - 'lib/bundler/cli/install.rb'
 
+# Offense count: 1
+Style/IfUnlessModifierOfIfUnless:
+  Exclude:
+    - 'spec/support/helpers.rb'
+
 # Offense count: 4
 # Cop supports --auto-correct.
 # Configuration parameters: SupportedStyles, IndentationWidth.
@@ -173,11 +176,10 @@ Style/ModuleFunction:
 Style/MultilineMethodCallIndentation:
   Enabled: false
 
-# Offense count: 5
+# Offense count: 4
 Style/NestedParenthesizedCalls:
   Exclude:
     - 'lib/bundler/resolver.rb'
-    - 'spec/bundler/shared_helpers_spec.rb'
     - 'spec/commands/lock_spec.rb'
     - 'spec/runtime/setup_spec.rb'
 
@@ -195,7 +197,7 @@ Style/PredicateName:
     - 'lib/bundler/source/git/git_proxy.rb'
     - 'lib/bundler/source/path.rb'
 
-# Offense count: 23
+# Offense count: 25
 # Configuration parameters: EnforcedStyle, SupportedStyles.
 # SupportedStyles: compact, exploded
 Style/RaiseArgs:

data/.travis.yml

@@ -26,7 +26,7 @@ addons:
       secure: "TrzIv116JLGUxm6PAUskCYrv8KTDguncKROVwbnjVPKTGDAgoDderd8JUdDEXrKoZ9qGLD2TPYKExt9/QDl71E+qHdWnVqWv4HKCUk2P9z/VLKzHuggOUBkCXiJUhjywUieCJhI3N92bfq2EjSBbu2/OFHqWOjLQ+QCooTEBjv8="
 
 rvm:
-  - 2.3.0
+  - 2.3.1
   - 2.2
   - 2.1
   - 2.0.0
@@ -39,7 +39,7 @@ env:
   # We need to know if changes to rubygems will break bundler on release
   - RGV=master
   # Test the latest rubygems release with all of our supported rubies
-  - RGV=v2.6.1
+  - RGV=v2.6.4
   - RGV=v2.4.8
 
 matrix:

data/CHANGELOG.md

@@ -1,7 +1,44 @@
-## 1.12.6 (2016-10-10)
+## 1.13.0.pre.1 (2016-06-20)
 
-Bugfixes:
-  - add support for weak etags to the new index (@segiddins)
+Performance:
+
+  - speed up gemfile resolution during `bundle install` by between 4x-100x (#4376, @segiddins)
+  - generally reduce object allocations when using bundler (@segiddins)
+  - speed up bin generation for path gems with many files (#2846, @segiddins)
+  - fix detecting path spec changes to avoid re-resolving unnecessarily (@jrafanie)
+
+Features:
+
+  - automatically trampoline to the bundler version locked in the lockfile, only updating to the running version on `bundle update --bundler` (@segiddins)
+  - laying the groundwork for plugin support, which is currently unsuppported, undocumented, disabled by default, and liable to change without notice (@asutoshpalai)
+  - allow `bundle viz --without` to accept multiple `:`-delimited groups (@mobilutz)
+  - support for RubyGems 2.6.4 (#4368, @segiddins, @RochesterinNYC)
+  - colorize updated gem versions (#4334, @bronzdoc)
+  - add the `--standalone` flag to `bundle binstubs` (#4594, @b-ggs)
+  - update the `bundle gem` CoC to contributor covenant v1.4 (@cllns)
+  - use a custom YAML serializer to make config file consistent (@segiddins)
+  - filter credentials from error messages (bundler/bundler-features#111, @RochesterinNYC, @sandlerr)
+  - support relative paths used inside a nested invocation of `eval_gemfile` (#4584, @RochesterinNYC)
+  - fail gracefully when attempting to install a yanked gem (#4344, @allenzhao)
+  - automatically install an inline gemfile when gems are missing locally (@segiddins)
+  - allow conflicts for gems resolved via `gemspec` (@segiddins)
+  - add `--add-platform` option to `bundle lock` (@segiddins)
+  - fail gracefully when a resolved spec's `required_ruby_version` or `required_rubygems_version` is incompatible (@segiddins)
+
+Bugfixes:
+
+  - implicitly unlock the resolved ruby version when the declared requirements in the gemfile are incompatible with the locked version (#4595, #4627, @segiddins)
+  - add support for quoted paths in `$PATH` (#4323, @segiddins)
+  - check out missing git repos that are not being installed (#3981, @asutoshpalai)
+  - write `bundler/setup.rb` to a consistent path (@glennpratt)
+  - open editor in `bundle open` with a clean environment (@sj26)
+  - resolve infinitely recursive copy when running `bundle package --all` with a `gemspec` in the gemfile (#4392, #4430, @RochesterinNYC)
+  - fail gracefully when encountering an `Errno::ENOTSUP` (#4394, @segiddins)
+  - fail gracefully when encountering an `Errno::EHOSTUNREACH` (#4642, @allenzhao)
+  - fix loading config files with very long values (#4370, @segiddins)
+  - only show potential updates for gemfile platforms in `bundle outdated` (#4450, @RochesterinNYC)
+  - allow running `bundle install --deployment` after `bundle package --all` with path gems (#2175, @allenzhao)
+  - add support for patchlevels in ruby versions in the gemfile and gemspecs (#4593, @chalkos)
 
 ## 1.12.5 (2016-05-25)
 

data/CONTRIBUTING.md

@@ -5,27 +5,31 @@ Bundler welcomes contributions from *everyone*. While contributing, please follo
 If you'd like to help make Bundler better, you totally rock! Here are some ways you can contribute:
 
   - by using prerelease versions (run `gem install bundler --pre`)
-  - by [reporting bugs you encounter](https://github.com/bundler/bundler/issues/new)
-  - by [suggesting new features](https://github.com/bundler/bundler-features/issues/new)
+  - by [reporting bugs you encounter or suggesting new features](https://github.com/bundler/bundler/issues/new)
   - by adding to or editing [the Bundler documentation website](http://bundler.io) and [Bundler man pages](http://bundler.io/man/bundle.1.html)
   - by [checking issues for completeness](https://github.com/bundler/bundler/blob/master/DEVELOPMENT.md#bug-triage)
   - by closing issues that are not complete
   - by adding a failing test for reproducible [reported bugs](https://github.com/bundler/bundler/issues)
   - by reviewing [pull requests](https://github.com/bundler/bundler/pulls) and suggesting improvements
-  - by improving existing code, including [suggestions from PullReview](https://www.pullreview.com/github/bundler/bundler/reviews/master)
+  - by improving existing code, including suggestions from [PullReview](https://www.pullreview.com/github/bundler/bundler/reviews/master) or [CodeClimate](https://codeclimate.com/github/bundler/bundler)
   - by [writing code](https://github.com/bundler/bundler/blob/master/DEVELOPMENT.md) (no patch is too small! fix typos or bad whitespace)
+  - by backfilling [unit tests](https://github.com/bundler/bundler/tree/master/spec/bundler) for modules that lack [coverage](https://codeclimate.com/github/bundler/bundler/coverage)
 
-If you need help getting started, check out the [DEVELOPMENT](https://github.com/bundler/bundler/blob/master/DEVELOPMENT.md) file for steps that will get you up and running.
+If you need help getting started, check out the [DEVELOPMENT.md](https://github.com/bundler/bundler/blob/master/DEVELOPMENT.md) file for steps that will get you up and running.
 
 Thanks for helping us make Bundler better.
 
+# Roadmap
+
+If you're interested in reading some of the potential ideas or plans for Bundler, see the official Bundler [Trello Board](https://trello.com/b/DioUaKgx/bundler).
+
 # Troubleshooting
 
 If you're having a problem, please see [ISSUES](https://github.com/bundler/bundler/blob/master/ISSUES.md) for troubleshooting steps and a guide for how to submit a ticket that will help us solve the problem you are having as quickly as possible.
 
 # Requesting Features
 
-Head on over to the [Bundler features](https://github.com/bundler/bundler-features) project, or any of the lists or channels listed below. Feature-wise we consider Bundler stable, so the core team does not tend to work on feature suggestions. Pull requests welcome though!
+Feel free to discuss your ideas or feature requests on any of the lists or channels listed below or [create an issue](https://github.com/bundler/bundler/issues/new) with the `feature-request` label. Feature-wise, we consider Bundler stable, so the core team does not tend to work on feature suggestions. Pull requests are welcome though!
 
 # Discussing Bundler
 

data/DEVELOPMENT.md

@@ -8,26 +8,33 @@ You can start learning about Bundler by reading [the documentation](http://bundl
 
 If you’re interested in contributing to Bundler, that’s awesome! We’d love your help.
 
-If you have any questions after reading this page, please feel free to contact either [@indirect](http://github.com/indirect) or [@hone](http://github.com/hone). They are both happy to provide help working through your first bugfix or thinking through the problem you’re trying to resolve.
+If you have any questions after reading this page, please feel free to contact either [@indirect](https://github.com/indirect), [@segiddins](https://github.com/segiddins), or [@RochesterinNYC](https://github.com/RochesterinNYC). They are all happy to provide help working through your first bug fix or thinking through the problem you’re trying to resolve.
 
 ## How you can help
 
-We track [small
-bugs](https://github.com/bundler/bundler/issues?labels=small&state=open) and [small features](https://github.com/bundler/bundler-features/issues?labels=small&state=open) so that anyone who wants to help can start with something that's not too overwhelming. We also keep a [list of things anyone can help with, any time](https://github.com/bundler/bundler/blob/master/CONTRIBUTING.md#contributing). If nothing on those lists looks good, talk to us, and we'll figure out what you can help with. We can absolutely use your help, no matter what level of programming skill you have at the moment.
+We track [small bugs and features](https://github.com/bundler/bundler/issues?labels=small) so that anyone who wants to help can start with something that's not too overwhelming. We also keep a [list of things anyone can help with, any time](https://github.com/bundler/bundler/blob/master/CONTRIBUTING.md#contributing). If nothing on those lists looks good, talk to us, and we'll figure out what you can help with. We can absolutely use your help, no matter what level of programming skill you have at the moment.
 
 # Development setup
 
 Bundler doesn't use a Gemfile to list development dependencies, because when we tried it we couldn't tell if we were awake or it was just another level of dreams. To work on Bundler, you'll probably want to do a couple of things.
 
-  1. Install Bundler's development dependencies
+  1. Install `groff-base` and `graphviz` packages using your package manager, e.g for ubuntu
 
-        $ rake spec:deps
+        $ sudo apt-get install graphviz groff-base -y
 
-  2. Run the test suite, to make sure things are working
+     and for OS X (with brew installed)
 
-        $ rake spec
+        $ brew install graphviz homebrew/dupes/groff
 
-  3. Set up a shell alias to run Bundler from your clone, e.g. a Bash alias:
+  2. Install Bundler's development dependencies
+
+        $ bin/rake spec:deps
+
+  3. Run the test suite, to make sure things are working
+
+        $ bin/rake spec
+
+  4. Set up a shell alias to run Bundler from your clone, e.g. a Bash alias:
 
         $ alias dbundle='ruby -I /path/to/bundler/lib /path/to/bundler/exe/bundle'
 
@@ -52,6 +59,14 @@ Before you submit a pull request, please remember to do the following:
         $ bin/rspec spec/bundler
         $ bin/rspec spec/commands/update_spec.rb
 
+- Please ensure that the commit messages included in the pull request __do not__ have the following:
+  - `@tag` Github user or team references (ex. `@indirect` or `@bundler/core`)
+  - `#id` references to issues or pull requests (ex. `#43` or `bundler/bundler-site#12`)
+
+  If you want to use these mechanisms, please instead include them in the pull request description. This prevents multiple notifications or references being created on commit rebases or pull request/branch force pushes.
+
+- Additionally, do not use `[ci skip]` or `[skip ci]` mechanisms in your pull request titles/descriptions or commit messages. Every potential commit and pull request should run through Bundler's CI system. This applies to all changes/commits (ex. even a change to just documentation or the removal of a comment).
+
 # Bug triage
 
 Triage is the work of processing tickets that have been opened into actionable issues, feature requests, or bug reports. That includes verifying bugs, categorizing the ticket, and ensuring there's enough information to reproduce the bug for anyone who wants to try to fix it.
@@ -83,15 +98,14 @@ If you can reproduce an issue, you're well on your way to fixing it. :) Fixing i
 Finally, the ticket may be a duplicate of another older ticket. If you notice a ticket is a duplicate, simply comment on the ticket noting the original ticket’s number. For example, you could say “This is a duplicate of issue #42, and can be closed”.
 
 
-# Adding new features
+# Adding New Features
 
 If you would like to add a new feature to Bundler, please follow these steps:
 
-  1. [Create an issue](https://github.com/bundler/bundler-features/issues/new) in the bundler-features repo to discuss your feature.
+  1. [Create an issue](https://github.com/bundler/bundler/issues/new) with the [`feature-request` label](https://github.com/bundler/bundler/labels/feature-request) to discuss your feature.
   2. Base your commits on the master branch, since we follow [SemVer](http://semver.org) and don't add new features to old releases.
   3. Commit the code and at least one test covering your changes to a feature branch in your fork.
-  4. Put a line in the [CHANGELOG](https://github.com/bundler/bundler/blob/master/CHANGELOG.md) summarizing your changes under the next release under the "Features" heading.
-  5. Send us a [pull request](https://help.github.com/articles/using-pull-requests) from your feature branch.
+  4. Send us a [pull request](https://help.github.com/articles/using-pull-requests) from your feature branch.
 
 If you don't hear back immediately, don’t get discouraged! We all have day jobs, but we respond to most tickets within a day or two.
 
@@ -114,7 +128,7 @@ Code needs explanation, and sometimes those who know the code well have trouble
 
 Bundler has two main sources of documentation: the built-in help (including usage information and man pages) and the [Bundler documentation site](http://bundler.io).
 
-If you’d like to submit a patch to the man pages, follow the steps for adding a feature above. All of the man pages are located in the `man` directory. Just use the “Documentation” heading when you describe what you did in the changelog.
+If you’d like to submit a patch to the man pages, follow the steps for submitting a pull request above. All of the man pages are located in the `man` directory. Just use the “Documentation” heading when you describe what you did in the changelog.
 
 If you have a suggestion or proposed change for [bundler.io](http://bundler.io), please open an issue or send a pull request to the [bundler-site](https://github.com/bundler/bundler-site) repository.
 
@@ -123,14 +137,12 @@ If you have a suggestion or proposed change for [bundler.io](http://bundler.io),
 
 Community is an important part of all we do. If you’d like to be part of the Bundler community, you can jump right in and start helping make Bundler better for everyone who uses it.
 
-It would be tremendously helpful to have more people answering questions about Bundler (and often simply about Rubygems or Ruby itself) in our [issue tracker](https://github.com/bundler/bundler/issues) or on [Stack Overflow](http://stackoverflow.com/questions/tagged/bundler).
+It would be tremendously helpful to have more people answering questions about Bundler (and often simply about [Rubygems](https://github.com/rubygems/rubygems) or Ruby itself) in our [issue tracker](https://github.com/bundler/bundler/issues) or on [Stack Overflow](http://stackoverflow.com/questions/tagged/bundler).
 
 Additional documentation and explanation is always helpful, too. If you have any suggestions for the Bundler website [bundler.io](http://bundler.io), we would absolutely love it if you opened an issue or pull request on the [bundler-site](https://github.com/bundler/bundler-site) repository.
 
 Finally, sharing your experiences and discoveries by writing them up is a valuable way to help others who have similar problems or experiences in the future. You can write a blog post, create an example and commit it to Github, take screenshots, or make videos.
 
-Examples of how Bundler is used help everyone, and we’ve discovered that people already use it in ways that we never imagined when we were writing it. If you’re still not sure what to write about, there are also several projects doing interesting things based on Bundler. They could probably use publicity too.
-
-If you let someone on the core team know you wrote about Bundler, we will add your post to the list of Bundler resources on the Github project wiki.
+Publishing examples of how Bundler is used helps everyone, and we’ve discovered that people already use it in ways that we never imagined when we were writing it. If you’re still not sure what to write about, there are also several projects doing interesting things based on Bundler. They could probably use publicity too.
 
-Finally, participate carefully in the  all contributors to the Bundler project must agree to the contributor [code of conduct](http://bundler.io/conduct.html). By participating in this project you agree to abide by its terms.
+Finally, all contributors to the Bundler project must agree to the contributor [code of conduct](http://bundler.io/conduct.html). By participating in this project you agree to abide by its terms.

data/ISSUES.md

@@ -2,52 +2,57 @@
 
 So! You're having problems with Bundler. This file is here to help. If you're running into an error, try reading the rest of this file for help. If you can't figure out how to solve your problem, there are also instructions on how to report a bug.
 
-**Please use the [Bundler
-Features](https://github.com/bundler/bundler-features) repo to suggest and
-discuss features. The bundler issue tracker is only for bugs.**
-
 ## Documentation
 
 Instructions for common Bundler uses can be found on the [Bundler documentation site](http://bundler.io/).
 
-Detailed information about each Bundler command, including help with common problems, can be found in the [Bundler man pages](http://bundler.io/man/bundle.1.html).
+Detailed information about each Bundler command, including help with common problems, can be found in the [Bundler man pages](http://bundler.io/man/bundle.1.html) or [Bundler Command Line Reference](http://bundler.io/v1.11/commands.html).
 
 ## Troubleshooting
 
 ### Heroku errors
 
-Please open a ticket with Heroku if you're having trouble deploying. They have a professional support team who can help you resolve Heroku issues far better than the Bundler team can. If the problem that you are having turns out to be a bug in Bundler itself, Heroku support can get the exact details to us.
+Please open a ticket with [Heroku](https://www.heroku.com) if you're having trouble deploying. They have a professional support team who can help you resolve Heroku issues far better than the Bundler team can. If the problem that you are having turns out to be a bug in Bundler itself, [Heroku support](https://www.heroku.com/support) can get the exact details to us.
 
 ### Other problems
 
-First, figure out exactly what it is that you're trying to do. Then, go to the [Bundler documentation website](http://bundler.io) and see if we have instructions on how to do that.
+First, figure out exactly what it is that you're trying to do (see [XY Problem](http://xyproblem.info/)). Then, go to the [Bundler documentation website](http://bundler.io) and see if we have instructions on how to do that.
 
 Second, check [the compatibility
 list](http://bundler.io/compatibility.html), and make sure that the version of Bundler that you are
-using works with the versions of Ruby and Rubygems that you are using.
+using works with the versions of Ruby and Rubygems that you are using. To see your versions:
+
+    # Bundler version
+    bundle -v
+
+    # Ruby version
+    ruby -v
 
-If the instructions don't work, or you can't find any instructions, you can try these troubleshooting steps:
+    # Rubygems version
+    gem -v
 
-    # remove user-specific gems and git repos
+If these instructions don't work, or you can't find any appropriate instructions, you can try these troubleshooting steps:
+
+    # Remove user-specific gems and git repos
     rm -rf ~/.bundle/ ~/.gem/bundler/ ~/.gems/cache/bundler/
 
-    # remove system-wide git repos and git checkouts
+    # Remove system-wide git repos and git checkouts
     rm -rf $GEM_HOME/bundler/ $GEM_HOME/cache/bundler/
 
-    # remove project-specific settings
+    # Remove project-specific settings
     rm -rf .bundle/
 
-    # remove project-specific cached gems and repos
+    # Remove project-specific cached gems and repos
     rm -rf vendor/cache/
 
-    # remove the saved resolve of the Gemfile
+    # Remove the saved resolve of the Gemfile
     rm -rf Gemfile.lock
 
-    # uninstall the rubygems-bundler and open_gem gems
+    # Uninstall the rubygems-bundler and open_gem gems
     rvm gemset use global # if using rvm
     gem uninstall rubygems-bundler open_gem
 
-    # try to install one more time
+    # Try to install one more time
     bundle install
 
 ## Reporting unresolved problems
@@ -72,8 +77,8 @@ If you are unable to do that, please include the following information in your r
 
 If your version of Bundler does not have the `bundle env` command, then please include:
 
- - Your Gemfile
- - Your Gemfile.lock
+ - Your `Gemfile`
+ - Your `Gemfile.lock`
  - Your Bundler configuration settings (run `bundle config`)
  - What version of bundler you are using (run `bundle -v`)
  - What version of Ruby you are using (run `ruby -v`)
@@ -84,10 +89,9 @@ If your version of Bundler does not have the `bundle env` command, then please i
 
 If you are using Rails 2.3, please also include:
 
-  - Your boot.rb file
-  - Your preinitializer.rb file
-  - Your environment.rb file
-
+  - Your `boot.rb` file
+  - Your `preinitializer.rb` file
+  - Your `environment.rb` file
 
 If you have either `rubygems-bundler` or `open_gem` installed, please try removing them and then following the troubleshooting steps above before opening a new ticket.
 

data/Rakefile

@@ -34,7 +34,7 @@ namespace :spec do
     deps = Hash[BUNDLER_SPEC.development_dependencies.map do |d|
       [d.name, d.requirement.to_s]
     end]
-    deps["rubocop"] ||= "= 0.37.1" if RUBY_VERSION >= "1.9.3" # can't go in the gemspec because of the ruby version requirement
+    deps["rubocop"] ||= "= 0.39.0" if RUBY_VERSION >= "1.9.3" # can't go in the gemspec because of the ruby version requirement
 
     # JRuby can't build ronn or rdiscount, so we skip that
     if defined?(RUBY_ENGINE) && RUBY_ENGINE == "jruby"
@@ -65,7 +65,7 @@ namespace :spec do
       sh "sudo apt-get install graphviz -y 2>&1 | tail -n 2"
 
       # Install the gems with a consistent version of RubyGems
-      sh "gem update --system 2.6.1"
+      sh "gem update --system 2.6.4"
 
       $LOAD_PATH.unshift("./spec")
       require "support/rubygems_ext"
@@ -88,7 +88,7 @@ begin
 
   if RUBY_VERSION >= "1.9.3"
     # can't go in the gemspec because of the ruby version requirement
-    gem "rubocop", "= 0.37.1"
+    gem "rubocop", "= 0.39.0"
     require "rubocop/rake_task"
     RuboCop::RakeTask.new
   end
@@ -122,7 +122,7 @@ begin
       rubyopt = ENV["RUBYOPT"]
       # When editing this list, also edit .travis.yml!
       branches = %w(master)
-      releases = %w(v1.3.6 v1.3.7 v1.4.2 v1.5.3 v1.6.2 v1.7.2 v1.8.29 v2.0.14 v2.1.11 v2.2.5 v2.4.8 v2.6.1)
+      releases = %w(v1.3.6 v1.3.7 v1.4.2 v1.5.3 v1.6.2 v1.7.2 v1.8.29 v2.0.14 v2.1.11 v2.2.5 v2.4.8 v2.6.4)
       (branches + releases).each do |rg|
         desc "Run specs with Rubygems #{rg}"
         RSpec::Core::RakeTask.new(rg) do |t|
@@ -296,10 +296,21 @@ begin
     lib.prefix = "Bundler"
     lib.vendor_lib = "lib/bundler/vendor/thor"
   end
+
+  Automatiek::RakeTask.new("postit") do |lib|
+    lib.download = { :github => "https://github.com/bundler/postit" }
+    lib.namespace = "PostIt"
+    lib.vendor_lib = "lib/bundler/vendor/postit"
+
+    def lib.namespace_files
+      process_files(namespace, "BundlerVendoredPostIt")
+    end
+  end
 rescue LoadError
   namespace :vendor do
     task(:molinillo) { abort "Install the automatiek gem to be able to vendor gems." }
     task(:thor) { abort "Install the automatiek gem to be able to vendor gems." }
+    task(:postit) { abort "Install the automatiek gem to be able to vendor gems." }
   end
 end