mirror of
https://github.com/ruby/ruby.git
synced 2022-11-09 12:17:21 -05:00
[rubygems/rubygems] Allow releasing with a rubygems pre version
This condition is too restrictive in my opinion. If a user has a pre
version of rubygems installed, she should be fully responsible for it,
and we shouldn't restrict any functionality.
Also, why is a new prerelease disallowed but an old prelease allowed, or
why is 2.0.0.rc2 explictly whitelisted? I believe this kind of
exceptions are one more reason to actually permit this.
7f77a77620
This commit is contained in:
parent
e323f50a9c
commit
054d99d95b
1 changed files with 0 additions and 19 deletions
|
@ -79,25 +79,6 @@ The push command will use ~/.gem/credentials to authenticate to a server, but yo
|
||||||
def send_gem(name)
|
def send_gem(name)
|
||||||
args = [:post, "api/v1/gems"]
|
args = [:post, "api/v1/gems"]
|
||||||
|
|
||||||
latest_rubygems_version = Gem.latest_rubygems_version
|
|
||||||
|
|
||||||
if latest_rubygems_version < Gem.rubygems_version and
|
|
||||||
Gem.rubygems_version.prerelease? and
|
|
||||||
Gem::Version.new('2.0.0.rc.2') != Gem.rubygems_version
|
|
||||||
alert_error <<-ERROR
|
|
||||||
You are using a beta release of RubyGems (#{Gem::VERSION}) which is not
|
|
||||||
allowed to push gems. Please downgrade or upgrade to a release version.
|
|
||||||
|
|
||||||
The latest released RubyGems version is #{latest_rubygems_version}
|
|
||||||
|
|
||||||
You can upgrade or downgrade to the latest release version with:
|
|
||||||
|
|
||||||
gem update --system=#{latest_rubygems_version}
|
|
||||||
|
|
||||||
ERROR
|
|
||||||
terminate_interaction 1
|
|
||||||
end
|
|
||||||
|
|
||||||
gem_data = Gem::Package.new(name)
|
gem_data = Gem::Package.new(name)
|
||||||
|
|
||||||
unless @host
|
unless @host
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue