Feature #38134
Drop Ruby 2.6 support
Status: | Closed | Start date: | ||
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | % Done: | 0% | ||
Category: | Ruby support | |||
Target version: | 5.1.0 | |||
Resolution: | Fixed |
Description
The normal maintenance phase of Ruby 2.7 ended on 2022-04-22 (see https://www.ruby-lang.org/en/news/2022/04/12/ruby-2-7-6-released/). And some gems dropped the support for Ruby 2.7.
Redmine currently supports Ruby 2.6, but this prevents us from updating some gems such as Rouge and Capybara.
Related issues
Associated revisions
Drop Ruby 2.6 support (#38134).
Ruby 2.7: Fix RuboCop offense Style/ArgumentsForwarding (#38134).
Ruby 2.7: Fix RuboCop offense Performance/MapCompact (#38134).
Ruby 2.7: Fix RuboCop offense Performance/BindCall (#38134).
Set RuboCop TargetRubyVersion to 2.7 (#38134).
History
#1
Updated by Go MAEDA about 1 month ago
- Tracker changed from Patch to Feature
#3
Updated by Go MAEDA 17 days ago
- Related to Feature #38099: Ruby 3.2 support added
#4
Updated by Go MAEDA 17 days ago
Go MAEDA wrote:
We have to update Nokogiri to 1.14.0 to support Ruby 3.2. However, Nokogiri 1.14.0 ended support for Ruby 2.6. Therefore, Redmine cannot continue to support Ruby 2.6 any longer.
Sorry, this is wrong. The trunk r22043 and later supports Ruby 3.2. This is because the Gemfile is written to use Nokogiri 1.13.10 only when Ruby 2.6 is used.
#5
Updated by Go MAEDA 17 days ago
Now Ruby 2.6 prevent us from upgrading Rouge.
For Rouge, I don't want to adopt the solution of installing different versions depending on the version of Ruby because the supported languages for syntax highlighting change depending on the installed Ruby. This is confusing for users.
#6
Updated by Go MAEDA 17 days ago
- File drop-ruby-2_6.patch
added
#7
Updated by Go MAEDA 16 days ago
SQLite3 also ended support for Ruby 2.6.
https://github.com/sparklemotion/sqlite3-ruby/blob/master/CHANGELOG.md#160--2023-01-13