From 054d99d95bc9d3c9481be3ea97dd16b39a4ba5bd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?David=20Rodr=C3=ADguez?= Date: Mon, 3 Feb 2020 18:48:44 +0100 Subject: [PATCH] [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. https://github.com/rubygems/rubygems/commit/7f77a77620 --- lib/rubygems/commands/push_command.rb | 19 ------------------- 1 file changed, 19 deletions(-) diff --git a/lib/rubygems/commands/push_command.rb b/lib/rubygems/commands/push_command.rb index 41e6c7ec30..fe8157e502 100644 --- a/lib/rubygems/commands/push_command.rb +++ b/lib/rubygems/commands/push_command.rb @@ -79,25 +79,6 @@ The push command will use ~/.gem/credentials to authenticate to a server, but yo def send_gem(name) 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) unless @host