Contour 1.1.2.pre not showing up on Bundle Update
Hi,
I recently pushed contour-1.1.2.pre to RubyGems.
It shows up fine here:
https://rubygems.org/gems/contour/versions/1.1.2.pre
And I can install it using
gem install contour --pre
However it is not showing up when using bundler (I don't think it's a bundler issue):
Bundler accesses the RubyGems API here:
https://rubygems.org/api/v1/dependencies?gems=contour
Doing a quick search shows no version 1.1.2.pre of contour (although I'd expect to see it there along with other prerelease versions of contour)
Bundler then fails and gives me:
Could not find gem 'contour (~> 1.1.2.pre) ruby' in the
gems available on this machine.
My guess is that contour wasn't added to the rubygems index?
Thanks! Any help appreciated.
Remo
Comments are currently closed for this discussion. You can start a new one.
2 Posted by remomueller on 10 Dec, 2012 02:40 PM
Update:
Yanked the gem to see if the index would refresh on the unyank:
gem yank contour -v1.1.2.pregem yank contour -v1.1.2.pre --undo(Did not work...)
3 Posted by remomueller on 10 Dec, 2012 03:09 PM
Opened an issue on Bundler also.
github.com/carlhuda/bundler/issues/2209
4 Posted by remomueller on 10 Dec, 2012 09:20 PM
Looks like this is more of a potential issue with RubyGems versioning and my understanding of Semantic Versioning.
It looks like prerelease is only recognized by RubyGems when the
minornumber is bumpedmajor.minor.patch-build.Ex:
1.0.0 => 1.1.0.preWhat apparently fails is:
1.0.0 => 1.0.1.preSo I guess it's my fault for wanting to do a prerelease on a
patchlevel version.Is there a reason why patch level pre-releases aren't considered pre-releases by RubyGems?
5 Posted by remomueller on 10 Dec, 2012 10:32 PM
Closing see:
https://github.com/carlhuda/bundler/issues/2209#issuecomment-11221526
Nick Quaranto closed this discussion on 19 Dec, 2012 01:34 AM.