Ruby just recently bump the master version to 3.0 and this version requirement in unicorn breaks our ruby-head CI.
I don't really see any reason to protect against newer Ruby version. From d1c43dd70b06543727ac88e3930caa0482558a6b Mon Sep 17 00:00:00 2001 From: Jean Boussier <[email protected]> Date: Tue, 1 Sep 2020 14:14:07 +0200 Subject: [PATCH] Update ruby_version requirement to allow ruby 3.0 --- unicorn.gemspec | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/unicorn.gemspec b/unicorn.gemspec index cbe855d..9a79055 100644 --- a/unicorn.gemspec +++ b/unicorn.gemspec @@ -25,10 +25,7 @@ s.homepage = 'https://yhbt.net/unicorn/' s.test_files = test_files - # technically we need ">= 1.9.3", too, but avoid the array here since - # old rubygems versions (1.8.23.2 at least) do not support multiple - # version requirements here. - s.required_ruby_version = '< 3.0' + s.required_ruby_version = '>= 1.9.3' # We do not have a hard dependency on rack, it's possible to load # things which respond to #call. HTTP status lines in responses -- 2.26.2
