livingsocial / bundler-patch

Update your gems conservatively to deal with vulnerable gems or just get more current.

livingsocial/bundler-patch Issues

Fully support Bundler 2
Updated 6 years ago1
Port behavior to bundler 2
Closed 8 years ago6
Checkout https://github.com/joonty/pessimize
Updated 7 years ago
Specifying -v is still updating all the gems.
Closed 7 years ago
BUG: Updating Gemfile for vuln update left line with incorrect syntax
Updated 7 years ago
--gemfile option can take a dir and just blink atchya
Closed 7 years ago
Not looking in target directory for .ruby-version if --gemfile?
Closed 7 years ago
Haven't figured out what to do if no Ruby version in Gemfile[.lock] and no .ruby-version.
Closed 7 years ago1
Don't keep re-executing target shell if rubies match.
Closed 7 years ago
New option to only update "proven" gems by date.
Updated 7 years ago
Reflect to stdout the open3 stuff.
Updated 7 years ago1
--gemfile without --use-target-ruby should warn if different Ruby.
Updated 7 years ago
Support --gemfile argument
Closed 7 years ago2
Update BUNDLER.md now that 1.14 is out
Closed 7 years ago
Change underscore options to hyphens
Closed 7 years ago
Align options with bundler patch-level options
Closed 7 years ago
--ruby AND --rubies is redundant - both are required now.
Updated 7 years ago
patch vulnerable not handling 4 digit version properly
Updated 7 years ago2
Ensure cache is updated after gems installed
Closed 8 years ago1
Ruby version updates shouldn't touch the file
Updated 8 years ago
Support all bundler-patch commands without installing gems
Closed 8 years ago2
Should it prevent reverting to older versions?
Updated 8 years ago
Cannot override advisory dir for ruby-advisory-db
Updated 8 years ago1
No option to use `-v` AND a list
Updated 8 years ago
bug running in gem dev
Updated 8 years ago1
If I change the Gemfile requirement to older gem, bundle patch doesn't work
Updated 8 years ago1
`--dry-run` to match outdated pretty & parseable
Closed 8 years ago1
If `-m` not used, but only minor increase is available, it looks like maybe it's broken since there's no feedback.
Updated 8 years ago
Support dry-run / outdated behavior to list what would be done
Updated 8 years ago
Warn on major version update
Updated 8 years ago
Output options in play
Updated 8 years ago
Cannot issue `bundle patch -h`
Updated 8 years ago
Is version comparison doing it by string ... :D
Closed 8 years ago1
why this WARN output?
Updated 8 years ago
--minor_preferred --strict_updates still allow a major version increment
Closed 8 years ago1
Research the --source hack
Closed 8 years ago2
Slop 4 is going to be a problem
Closed 8 years ago
Vulnerability code will update gem requirement, broaden into an option.
Updated 8 years ago
Consider PR to bundler proper for conservative upgrade
Closed 8 years ago
Support 1.11.x of Bundler
Closed 8 years ago1
change bin to `bundler-patch` from `bundle-patch`
Closed 8 years ago1
Redo the command names
Closed 8 years ago1
I have Rails 4.2.6 installed, why is scan telling me about older rails vulns?
Closed 8 years ago1