bundleup

This is a gem housekeeping release. There should be no user-facing changes.

🏠 Housekeeping

• Update rubocop requirement from 1.12.0 to 1.12.1 (#115) @dependabot

• Drop support for Ruby < 2.3

• Fix erroneous blank lines in output

• #1: If a Gemfile has an inline or prefix comment for a particular gem, and that gem is being held back due to a pin, then print the comment along with the pin information in bundleup's output.

• You can now pass command-line arguments to bundleup, which will in turn be
  handed to bundle update. For example: bundleup --group=development.
• Improve the console output when a Bundler command fails.
• Fixed a bug where if a Bundler command failed to run, it would be executed a
  second time.

• Change the upgrade process to modify the Gemfile.lock in place, with the
  option to "undo" (i.e. restore from backup) if the changes are not desired.
  This makes bundleup much faster since it doesn't have to run bundle update
  twice.
• Fixed a bug where color was mistakenly based on the newest version of a gem,
  even if a restriction prevented upgrading to that version.

• Always show SHA changes in red. If a dependency is tracking a
  Git branch, and running bundle update would cause that branch
  to updated and point to a new ref, that is something that
  warrants attention.

• Animated spinner during long-running bundler commands
• Rather than run bundle in a temp directory, run within the current
  directory, making a backup copy of Gemfile.lock. This ensures that relative
  paths and .bundle/config are honored.

• Initial release