bundleup 2.3.0 → 2.4.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: cc1297e37c324c0e1a7211bbd56afdb0112e926f2f36e57497ac4f82a485b429
-  data.tar.gz: fdd2d8e71d312d5bb0a5d3f4f73c8b072fecf8c94bebe67098c6584c18d5c402
+  metadata.gz: 2dfa7a68f9a4f6cb80f944a05711bc3baf21d7d4771b1fe517eaa1e87ccf5879
+  data.tar.gz: ec24af12b0c552fd3649461559681141d681f4eb922b978701203e0c3c4e9235
 SHA512:
-  metadata.gz: b8d980c979d30a1a016a21acf8a82bd0f809ce589d676e328e27adaf2b913f582ee4a879fb5a9485a7535ea80485dc4391d86c345249e654b3807cdf2e8d1e1a
-  data.tar.gz: 3f9302208de8f051fd829dc438498f8802bf9660e80e90fa79c4ee496e4c867b7b86cabd6f9ef45ab60f8fd6bce16ac147294779cf9a049f02878845a6f1dd54
+  metadata.gz: 6622f460ab1d5bfde0f40ca4f2a4c9332556c4bcaf345e3d3be59c19565138acec061665c976e15db5f9419989122bf1e37d3efe0a6080e28c948b9964987869
+  data.tar.gz: d857ee33151444717cbc58d7d3af5d8650e7f906022c70d20f18ffdf91d803b53d0ea810df797f9961c56c19c5d012781cfed733f4bfc167bfcbb7b62a5817e6

data/README.md

@@ -75,6 +75,38 @@ Note that `--update-gemfile` will _not_ modify Gemfile entries that contain a co
 gem 'sidekiq', '~> 5.2' # our monkey patch doesn't work on 6.0+
 ```
 
+### Integrate bundlup in a script
+
+`Bundleup::CLI` gives you two methods to track updated and pinned gems:
+
+```ruby
+cli = Bundleup::CLI.new([])
+cli.run
+cli.updated_gems
+# > ["rubocop"]
+
+cli.pinned_gems
+# > ["rake"]
+```
+
+You can then easily create scripts to perform any actions such as running tests, running rubocop, or commit changes.
+
+```ruby
+cli = Bundleup::CLI.new([])
+cli.run
+
+if cli.updated_gems.any?
+  system "bundle exec rspec"
+elsif cli.updated_gems.include?("rubocop")
+  system "bundle exec rubocop"
+end
+
+if cli.updated_gems.any?
+  system "git commit -m \"Update gems dependencies\" -- Gemfile.lock"
+end
+```
+
+
 ## How bundleup works
 
 bundleup starts by making a backup copy of your Gemfile.lock. Next it runs `bundle check` (and `bundle install` if any gems are missing in your local environment), `bundle list`, then `bundle update` and `bundle list` again to find what gems versions are being used before and after Bundler does its updating magic. (Since gems are actually being installed into your Ruby environment during these steps, the process may take a few moments to complete, especially if gems with native extensions need to be compiled.)

data/lib/bundleup/cli.rb

@@ -8,14 +8,21 @@ module Bundleup
     extend Forwardable
     def_delegators :Bundleup, :commands, :logger
 
+    attr_reader :updated_gems, :pinned_gems
+
     def initialize(args)
       @args = args.dup
       @update_gemfile = @args.delete("--update-gemfile")
+      @updated_gems = []
+      @pinned_gems = []
     end
 
     def run # rubocop:disable Metrics/AbcSize, Metrics/MethodLength
       print_usage && return if (args & %w[-h --help]).any?
 
+      @updated_gems = []
+      @pinned_gems = []
+
       assert_gemfile_and_lock_exist!
 
       logger.puts "Please wait a moment while I upgrade your Gemfile.lock..."
@@ -32,6 +39,9 @@ module Bundleup
           logger.puts pin_report unless pin_report.empty?
 
           if logger.confirm?("Do you want to apply these changes?")
+            @updated_gems = update_report.updated_gems
+            @pinned_gems = pin_report.pinned_gems
+
             logger.ok "Done!"
           else
             backup.restore

data/lib/bundleup/pin_report.rb

@@ -24,6 +24,10 @@ module Bundleup
       end
     end
 
+    def pinned_gems
+      outdated_gems.keys.sort
+    end
+
     private
 
     attr_reader :gem_versions, :outdated_gems, :gem_comments

data/lib/bundleup/update_report.rb

@@ -25,6 +25,12 @@ module Bundleup
       end
     end
 
+    def updated_gems
+      gem_names.reject do |gem|
+        old_versions[gem] == new_versions[gem]
+      end
+    end
+
     private
 
     attr_reader :old_versions, :new_versions

data/lib/bundleup/version.rb

@@ -1,3 +1,3 @@
 module Bundleup
-  VERSION = "2.3.0".freeze
+  VERSION = "2.4.0".freeze
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: bundleup
 version: !ruby/object:Gem::Version
-  version: 2.3.0
+  version: 2.4.0
 platform: ruby
 authors:
 - Matt Brictson
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2023-07-15 00:00:00.000000000 Z
+date: 2023-08-22 00:00:00.000000000 Z
 dependencies: []
 description: Use `bundleup` whenever you want to update the locked Gemfile dependencies
   of a Ruby project. It shows exactly what gems will be updated with color output
@@ -63,7 +63,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.4.15
+rubygems_version: 3.4.18
 signing_key:
 specification_version: 4
 summary: A friendlier command-line interface for Bundler’s `update` and `outdated`