From 07a79b30cd18d2d28bd62dae0d4674c95e1127ec Mon Sep 17 00:00:00 2001 From: Igor Fedoronchuk Date: Thu, 1 Oct 2026 13:31:04 +0200 Subject: [PATCH 1/3] ci: drop EOL Ruby and Rails from the matrix Ruby 3.2 reached end of life on 2026-03-31; Rails 7.1 on 2025-10-01 and 7.2 on 2026-08-09 (endoflife.date). The matrix now covers Ruby 3.3/3.4/4.0 against Rails 8.0 and 8.1. Both Active Admin versions stay and the matrix has no excludes at all. The two it carried claimed "Active Admin 3.2 predates Rails 8 support", which is not what happens: AA 3.2.5 installs and the full suite passes on both Rails 8.0.5.1 and 8.1.4, so the rules were removing real coverage. The Gemfile's local default Rails is now 8.0.0 so a bare `bundle install` no longer resolves an EOL Rails. --- .github/workflows/ci.yml | 10 ++-------- Gemfile | 2 +- 2 files changed, 3 insertions(+), 9 deletions(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index cfee892..772f701 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -14,15 +14,9 @@ jobs: strategy: fail-fast: false matrix: - ruby: ['3.2', '3.3', '3.4'] - rails: ['7.1.0', '7.2.0', '8.0.0', '8.1.0'] + ruby: ['3.3', '3.4', '4.0'] + rails: ['8.0.0', '8.1.0'] activeadmin: ['3.2.0', '3.5.0'] - exclude: - # Active Admin 3.2 predates Rails 8 support. - - rails: '8.0.0' - activeadmin: '3.2.0' - - rails: '8.1.0' - activeadmin: '3.2.0' env: RAILS: ${{ matrix.rails }} AA: ${{ matrix.activeadmin }} diff --git a/Gemfile b/Gemfile index 0955c81..d2ed288 100644 --- a/Gemfile +++ b/Gemfile @@ -3,7 +3,7 @@ source 'https://rubygems.org' # Specify your gem's dependencies in active_admin_date_range_preset.gemspec gemspec -default_rails_version = '7.1.0' +default_rails_version = '8.0.0' default_activeadmin_version = '3.5.0' gem 'rails', "~> #{ENV['RAILS'] || default_rails_version}" From 7aefd2f671c5de39ca546b4b93ddf9d8ee4b64cd Mon Sep 17 00:00:00 2001 From: Igor Fedoronchuk Date: Thu, 1 Oct 2026 13:31:04 +0200 Subject: [PATCH 2/3] chore: declare the supported Ruby floor in the gemspec MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit required_ruby_version moves from >= 3.2 to >= 3.3 to match what CI tests now that Ruby 3.2 is end of life. The activeadmin and railties dependency ranges are untouched. No Active Admin version was dropped from the matrix, and narrowing the tested Rails range is not evidence the gem stopped working on older Rails — raising a runtime floor would break consumers for nothing. No version bump, no release. --- README.md | 8 +++++--- active_admin_date_range_preset.gemspec | 2 +- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index dc2959d..3b645d6 100644 --- a/README.md +++ b/README.md @@ -19,9 +19,11 @@ This is how it looks like ## Compatibility -Active Admin 3.2 or newer, in the 3.x series. Rails 7.1 or newer, Ruby 3.2 or -newer. CI covers Active Admin 3.2 and 3.5 against the Rails versions in the -matrix. +Active Admin 3.2 or newer, in the 3.x series. Rails 7.1 or newer, Ruby 3.3 or +newer. CI covers Active Admin 3.2 and 3.5 on Ruby 3.3, 3.4 and 4.0 against +Rails 8.0 and 8.1 — the Rails releases still supported upstream. The declared +`railties >= 7.1` floor is left as it is: dropping a version from CI is not +evidence the gem broke there. The Rails and Ruby floors are declared explicitly because Active Admin 3.2 still allows `railties >= 6.1` and Ruby `>= 2.6`, both long past end of life diff --git a/active_admin_date_range_preset.gemspec b/active_admin_date_range_preset.gemspec index 689cb4a..beb986d 100644 --- a/active_admin_date_range_preset.gemspec +++ b/active_admin_date_range_preset.gemspec @@ -35,7 +35,7 @@ Gem::Specification.new do |spec| # both of which reached end of life years ago and neither of which is # tested here. Without these the gem would inherit that claim by silence. spec.add_dependency "railties", ">= 7.1" - spec.required_ruby_version = ">= 3.2" + spec.required_ruby_version = ">= 3.3" spec.add_development_dependency "rake" end From fbd50a25cfd57d766cacabc4584a46311994bed5 Mon Sep 17 00:00:00 2001 From: Igor Fedoronchuk Date: Thu, 1 Oct 2026 14:26:25 +0200 Subject: [PATCH 3/3] Raise the Rails floor to match what is tested The matrix now stops at Rails 8.0, but the gemspec still declared railties >= 7.1 and the README still promised "Rails 7.1 or newer". That left the declared floor untested, which is the exact gap the explicit floors were added to close -- the paragraph directly below the claim says so, about Active Admin's own railties >= 6.1. The same question was already answered the other way in this branch for Ruby: CI moved to 3.3+, so the floor moved to 3.3. Rails gets the same treatment. Every Rails 7.x series is out of support -- 7.1 since October 2025, 7.2 since August 2026 -- so nothing being dropped was receiving security fixes. Dropping a supported version is user-visible, so bump the minor to 0.4.0 in both the gem and the npm package, and say in the README that 0.3.x is where Rails 7 users stay. --- README.md | 10 ++++++---- active_admin_date_range_preset.gemspec | 7 ++++--- lib/active_admin_date_range_preset/version.rb | 2 +- package.json | 2 +- 4 files changed, 12 insertions(+), 9 deletions(-) diff --git a/README.md b/README.md index 3b645d6..8f0b7c8 100644 --- a/README.md +++ b/README.md @@ -19,11 +19,13 @@ This is how it looks like ## Compatibility -Active Admin 3.2 or newer, in the 3.x series. Rails 7.1 or newer, Ruby 3.3 or +Active Admin 3.2 or newer, in the 3.x series. Rails 8.0 or newer, Ruby 3.3 or newer. CI covers Active Admin 3.2 and 3.5 on Ruby 3.3, 3.4 and 4.0 against -Rails 8.0 and 8.1 — the Rails releases still supported upstream. The declared -`railties >= 7.1` floor is left as it is: dropping a version from CI is not -evidence the gem broke there. +Rails 8.0 and 8.1 — every Rails series still supported upstream. + +Version 0.4.0 raised the Rails floor from 7.1 to 8.0. Every 7.x series is out +of support — 7.1 since October 2025, 7.2 since August 2026 — and none of them +is tested. Stay on 0.3.x if you are still on Rails 7. The Rails and Ruby floors are declared explicitly because Active Admin 3.2 still allows `railties >= 6.1` and Ruby `>= 2.6`, both long past end of life diff --git a/active_admin_date_range_preset.gemspec b/active_admin_date_range_preset.gemspec index beb986d..9dada67 100644 --- a/active_admin_date_range_preset.gemspec +++ b/active_admin_date_range_preset.gemspec @@ -32,9 +32,10 @@ Gem::Specification.new do |spec| spec.add_dependency "activeadmin", "~> 3.2" # Active Admin 3.2 itself still allows railties >= 6.1 and Ruby >= 2.6, - # both of which reached end of life years ago and neither of which is - # tested here. Without these the gem would inherit that claim by silence. - spec.add_dependency "railties", ">= 7.1" + # both of which reached end of life years ago. Declare what CI covers, so + # the gem does not inherit that claim by silence. Every Rails 7.x series is + # out of support: 7.1 since October 2025, 7.2 since August 2026. + spec.add_dependency "railties", ">= 8.0" spec.required_ruby_version = ">= 3.3" spec.add_development_dependency "rake" diff --git a/lib/active_admin_date_range_preset/version.rb b/lib/active_admin_date_range_preset/version.rb index 2a65ec9..1c60b15 100644 --- a/lib/active_admin_date_range_preset/version.rb +++ b/lib/active_admin_date_range_preset/version.rb @@ -1,3 +1,3 @@ module ActiveAdminDateRangePreset - VERSION = "0.3.1" + VERSION = "0.4.0" end diff --git a/package.json b/package.json index 4481cbd..7124a6e 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "@activeadmin-plugins/active_admin_date_range_preset", - "version": "0.3.1", + "version": "0.4.0", "description": "Integrate useful fast links to set date ranges in to ActiveAdmin, for example today range, week range, month range", "main": "src/active_admin_date_range_preset.js", "style": "src/active_admin_date_range_preset.scss",