git-lite-version-bump 0.17.0 → 0.17.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 27079410bd5e17df87c9feb9cdc20c9d6e158bb6aa7b76c86c324f9a6cffe2a4
-  data.tar.gz: 43757821844c2f9847d8c8601c51fa9e49b2f620a77d93caf54a1b4cec798dc6
+  metadata.gz: 245fa58c69c2530bf29a431acafb3d1c2072dd685322efe95f2e0a486f57a050
+  data.tar.gz: 9a2b6c6cab12d189fdf6e85ff769bffaa64a1ca0d301f5712e2cd124fb5e9528
 SHA512:
-  metadata.gz: f13c494b1d02d9db46399671705dde89751cc753cad10f030c4b3251b9d331422fa843fde288374ec227143aea09866e1d60e562c767a4e26ba78ef3d6087837
-  data.tar.gz: 5e7b928a415dbf37f7c619e04271ba79290c81f6b773da3f4f31c6c4b7fc7bce3640f171dae04f33098133c52833f24ffbadceb991ec31b4bbee87619add4a5a
+  metadata.gz: 55b0499ada73ff1ee43db28d8388235dde7c2ebe2e36aed80630d61ac1c59a12e942a8ba9461103e02759e093b54dfe10141b664cd52351a70c743c16bae9b6c
+  data.tar.gz: 5c939fe28ce4faba2fda3016b827b407fbeeb7c021dae79a41316825fae1e256ff0364a35c43dc00e9d6c232d9e2f52f49ef8580c5611d3f8196e0b11e711a85

data/lib/git-version-bump.rb

@@ -252,9 +252,14 @@ module GitVersionBump
 		# within this file, we can't just look at Gem.location_of_caller, but
 		# instead we need to parse the caller stack ourselves to find which
 		# gem we're trying to version all over.
+		#
+		# Caller returns paths of the form `/path/to/file:100:in method...` on *nix
+		# and `C:\path\to\file:in method...` on Windows. Splitting on colon isn't
+		# reliable since the Windows path has a colon at the beginning, split on :num:
+		# instead since that will always be there no matter the platform.
 		Pathname(
 		  caller.
-		  map  { |l| l.split(':')[0] }.
+		  map  { |l| l.split(/:\d+:/)[0] }.
 		  find { |l| l != __FILE__ }
 		).realpath.to_s rescue nil
 	end
@@ -265,8 +270,16 @@ module GitVersionBump
 		# Grovel through all the loaded gems to try and find the gem
 		# that contains the caller's file.
 		Gem.loaded_specs.values.each do |spec|
-			search_dirs = spec.require_paths.map { |d| "#{spec.full_gem_path}/#{d}" } +
-			              [File.join(spec.full_gem_path, spec.bindir)]
+			# On Windows I have encountered gems that already have an absolute
+			# path, verify that the path is relative before appending to it
+			search_dirs = spec.require_paths.map do |path|
+				if Pathname(path).absolute?
+					path
+				else
+					File.join(spec.full_gem_path, path)
+				end
+			end
+			search_dirs << File.join(spec.full_gem_path, spec.bindir)
 			search_dirs.map! do |d|
 				begin
 					Pathname(d).realpath.to_s

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: git-lite-version-bump
 version: !ruby/object:Gem::Version
-  version: 0.17.0
+  version: 0.17.1
 platform: ruby
 authors:
 - Matt Palmer
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2020-03-31 00:00:00.000000000 Z
+date: 2020-05-06 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: github-release
@@ -102,7 +102,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.0.3
+rubygems_version: 3.1.2
 signing_key: 
 specification_version: 4
 summary: Manage your app version entirely via git tags (even lite tags)