mattbrictson / bundleup Goto Github PK

Thanks. README states that feature ideas shall be created as tickets here.

My current workflow was bundle outdated # --filter-major and then copy-paste its output to gem compare.
https://github.com/fedora-ruby/gem-compare

Also, we usually do it in batches (not all at once), in order to have separate CI runs and see green for each updated gem (or small group of gems).

Given an existing Gemfile and Gemfile.lock, if any of the dependency versions specified in the lock file are not already installed, then bundle list will fail. This causes bundleup to crash with a message like:

Failed to execute: bundle list (RuntimeError)

Possible solutions:

• bundleup could rescue this error and print a more informative error message.
• bundleup could rescue this error and automatically run bundle install to install the missing dependencies.
• bundleup could always start by running bundle check || bundle install to test that all dependencies are present – and install any that are missing – before proceeding.

Inspired by npm-check-updates I think that having here also interactive mode would be great 🙂

Thanks for the amazing gem!

The gem_updater project automates updating gems, including links to gem changelogs. It would be nice to merge this in as well!

bundleup incorrectly expects Gemfile and Gemfile.lock to be present in a project is using gems.rb and gems.lock files.

Expected behaviour:

Correctly detect and update gems.rb and gems.lock file.

When a "pin" in a Gemfile prevents a gem from being upgraded, bundleup displays a message like this:

Note that the following gem(s) are being held back:

friendly_id    5.1.0 → 5.2.3 : pinned at ~> 5.1.0
rbnacl         3.4.0 → 5.0.0 : pinned at ~> 3.4  
secure_headers 3.7.1 → 4.0.0 : pinned at ~> 3.3  

It would be nice if bundleup could display further information about why each gem is pinned. We can do this if there is a comment in the Gemfile explaining the pin.

For example, if the Gemfile has this:

gem "rbnacl", "~> 3.4" # Version 4+ is not compatible with net-ssh

Then perhaps bundleup could notice that comment and include it in its output:

Note that the following gem(s) are being held back:

friendly_id    5.1.0 → 5.2.3 : pinned at ~> 5.1.0
rbnacl         3.4.0 → 5.0.0 : pinned at ~> 3.4   # Version 4+ is not compatible with net-ssh
secure_headers 3.7.1 → 4.0.0 : pinned at ~> 3.3  

Great project! I believe this could soon be integrated into bundler itself. Wait and see!

I've tested bundle-auto-update and quite enjoyed the automated version increment -> test -> commit, but didn't have many gems to update, and since the project isn't maintained anymore I didn't want to rely on it too much.

I'd love to see this tool use the same patch/minor/major -> test -> commit workflow.