Version releases to Rubygems aren't working right.
shekibobo opened this issue · comments
As mentioned in #35.
Version bumps should be made in their own commits. I'm not sure what the problem is with pushing official releases, but I've never been able to use the RubyGems version of navigasmic, and always had to use the github source. It seems like new versions are still just pushing up older releases with the new version name.
See this comment for details as to what we see on RubyGems.
@TigerWolf If you bundle open navigasmic when using the RubyGems source, what does lib/navigasmic/version.rb show as the version number? What does the Gemfile.lock show?
This was the two commits:
-> % cat ~/.rvm/gems/ruby-2.0.0-p353@dc3/gems/navigasmic-1.0.5/lib/navigasmic/version.rb
module Navigasmic
VERSION = '1.0.5'
end
-> % cat ~/.rvm/gems/ruby-2.0.0-p353@dc3/gems/navigasmic-1.0.4/lib/navigasmic/version.rb
module Navigasmic
VERSION = '1.0.4'
end
released 1.1.0.. tell me how that goes.
This is still what I'm seeing on RubyGems.org
What commands are you using when you create/push the gem?
Ignore the date — is it different? the size is different.
Yeah, it seems like it's working alright when I use the RubyGems version now.
gem 'navigasmic', '~> 1.1.0'Any idea why it's not getting the dates right? It's misleading and confusing like that.
because that was hardcoded in the gem spec.