chrismo

A ruby app with .ruby-version 2.3.1, run `bundle patch -v -r --rubies 2.3.1` - no content changes, BUT the timestamp on the .ruby-version file is touched. That will cause the...

It currently still does that. I had a TODO to remove the note in the README, but the code is still there. I remmed out the functionality, but no tests...

Cannot override advisory dir for ruby-advisory-db

1

bundler-advise can be configured, but bundler-patch does not surface a way to redirect where bundler-advise's checkout path is located.

which was the intent of the flag - but currently am wanting to feed it -v AND rails since none of the security vulns show up with rails, but always...

bug running in gem dev

1

``` No known vulnerabilities to update. Updating 'bundler-fixture' conservatively. Fetching gem metadata from https://rubygems.org/......... Fetching version metadata from https://rubygems.org/.. /Users/chrismo/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/bundler-1.11.2/lib/bundler/resolver.rb:354:in `block in verify_gemfile_dependencies_are_found!': Could not find gem 'bundler-advise' in source...

If I change the Gemfile requirement to older gem, bundle patch doesn't work

1

Not sure if it should in this case, since `bundle` itself should be fine?

Be nice to confirm the options in effect in the header output

Bundler has this issue https://github.com/bundler/bundler/issues/4515 - would make sense here as well, both for #13 and #14.

bundler-patch 0.7.2 ``` * Could not attempt upgrade for mail from 1.0.0 to any patched versions 2.6.0, 2.2.15, 2.4.4. Most often this is because a major version increment would be...