Update bundler-1.16.6

[hsbt]

Description:

---

Tasks:

• Describe the problem / feature
• Write tests
• Write code to solve the problem
• Get code review from coworkers / friends

I will abide by the code of conduct.

[colby-swandale]

did i break something in this release?

[segiddins]

Looks like a test just needs to handle not being in a git repo, or something?

[hsbt]

@segiddins Yes, But Bundler-1.16.4 with RubyGems master passes the same example. Do we have some regression with Bundler-1.16.5 or 1.16.6?

[hsbt]

Also failed #2429

[indirect]

This is not a regression, but it's a change in the way that Bundler handles printing version numbers when Bundler itself is not inside a git repo. We can update the test 👍

[indirect]

@hsbt @colby-swandale I fixed it! rubygems/bundler#6737 After we backport the commit to 1-16-stable, I think it's fine to update the submodule to point to that commit, rather than doing an entire Bundler release just for a fix that only works when Bundler is a submodule in RubyGems.

[hsbt]

@indirect I agreed your suggestion. I will update submodule after updating to 1-16-stable branch in bundler and release rubygems 2.7.8.

[hsbt]

@indirect @colby-swandale Still failing with 1-16-stable branch. I can release RG 2.7.8 with Bundler 1.16.6, But I hope to resolve this failure because it's also failing with Bundler 1.17.0 or 2.0.0.

[colby-swandale]

Sorry for this to take so long @hsbt i will make this my number 1 issue to resolve.

[colby-swandale]

I'm a bit confused as to what's happening here. The test is passing on my local machine and looking into the report on travis, it seems to be reporting for a different commit c6bdddd

[hsbt]

@bundlerbot r+

[ghost]

Build succeeded

• continuous-integration/travis-ci/push