concerns_on_rails 1.28.9 → 1.29.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: f292a3f1cf7d1fae3b1e47be9daa416ae0b6c8b69ce0d4fd2efd583496f2d9aa
-  data.tar.gz: 661ffce3f3fa4fb305957b239fbb560752ea22f369da3268d03575efb35701da
+  metadata.gz: f00644495f4a20c3265cfa9289708136b4bb086aebeeb16026ebd2c9e12f7991
+  data.tar.gz: 01162f76ade27fb2b42aa93c3317819fb4db96c761717fdc20cafeedd213046f
 SHA512:
-  metadata.gz: a49931859e637327e55313e7473236a4ceca6a5f61c01f7f701a7d7acba317c8fe6a83ec05ec2dafa5d7e61da45d8d2623a26f15a876d9e7d12036cd9c40c451
-  data.tar.gz: 625395f36729c2d789b303cfeec6537dfa173364b70c0a6c971707616a0fb3161d5eef083417aadcc9586a7b99c89d9a7617355e08284cdb76d210a62a3df82f
+  metadata.gz: fad1b9c385054e869d5dcd4012f1e06182b3597c63a500d6513521fbefd758480ffcaf85922c0d805a2d1b07430f03a3d0a3fb1184f510450adfabd311155630
+  data.tar.gz: e7a299357dc9f389a4e9e99241af15c783806a96dc4b9037fe5283d1737038b63f53224a3c6e77e5f5b0a926e3d341df435c8c7b0d319a73258b33a489a15614

data/CHANGELOG.md

@@ -1,5 +1,51 @@
 <!-- CHANGELOG.md -->
 
+## 1.29.0 (2026-09-21)
+
+CI now runs **every Rails line the gemspec admits** — 6.0, 6.1, 7.0, 7.1, 7.2, 8.0 and 8.1 —
+where it previously ran 7.0 through 8.0. Extending the matrix downwards found 201 failures
+on the two new old lines and 0 on the new top line; all of them are fixed, and all seven
+legs are green and blocking.
+
+### Changed
+- **Rails 5.x is no longer declared.** The `actionpack` / `activerecord` / `activesupport`
+  floor moves from `>= 5.0` to `>= 6.0`. This drops nothing that ever worked: with
+  `required_ruby_version = ">= 3.2.0"`, the `>= 5.0` half was unreachable by construction —
+  Ruby 3's keyword-argument separation breaks Active Record 5.2's own `create_table`
+  (`schema_statements.rb:290`), so no bundle could satisfy both. Verified rather than
+  assumed: on Ruby 3.2 the suite fails 1,302 examples on Rails 5.2, every one of them
+  inside the framework.
+
+### Fixed
+- **Controllers::Includable**: `?fields[table]=...` raised `LocalJumpError` ("no block
+  given") on Rails 6.0. `requested_fields` called the block-less `params[:fields].each_pair`
+  and chained `with_object`, but `ActionController::Parameters#each_pair` only began
+  returning an Enumerator in 6.1. It now iterates with a block, which behaves the same on
+  every line.
+- **Models::Searchable**: the generated `search` scope raised
+  `ArgumentError: wrong number of arguments (given 2, expected 1)` for every call on Rails
+  6.0. Rails 6.0 forwards a scope's arguments through `define_method(name) { |*args| }`
+  with no `ruby2_keywords`, so under Ruby 3 the `ranked:` keyword reaches the body as a
+  trailing positional Hash. The scope now takes its options positionally and splats them
+  back out — same call signature, and an unknown key still raises.
+
+### Documented
+- Two features need a line newer than the 6.0 floor, and both now say so in the README's
+  compatibility table and in their own docs: `Controllers::Sortable`'s `nulls:` ordering
+  (Rails 6.1+, already raised at macro time) and `Models::Aliasable`'s **query side**
+  (Rails 6.1+ — resolving a `where`-hash key to an association, which is what makes Rails
+  alias the join, landed in 6.1; Aliasable's read/write side works on 6.0).
+
+### Internal
+- `gemfiles/rails_6.0.gemfile`, `rails_6.1.gemfile` and `rails_8.1.gemfile`; every gemfile
+  below 7.1 now pins `concurrent-ruby < 1.3.5`, which dropped its own `require "logger"`
+  that Active Support only started doing for itself in 7.1.
+- The spec harness clears Active Record's schema cache and (on <= 6.1)
+  `ActiveSupport::Dependencies::Reference` between examples, gives anonymous spec models a
+  `model_name`, and gains a `min_rails:` metadata tag for examples whose feature is version
+  gated. Without the first two, specs that reuse table and model names across files saw the
+  PREVIOUS file's columns and classes on 6.0/6.1.
+
 ## 1.28.9 (2026-09-19)
 
 CI now runs the matrix the gemspec actually claims: Rails 7.0–8.0 across Ruby 3.2/3.3/3.4,

data/README.md

@@ -11,7 +11,7 @@ One `include`, one declarative macro — done.
 [![CI](https://github.com/VSN2015/concerns_on_rails/actions/workflows/ci.yml/badge.svg)](https://github.com/VSN2015/concerns_on_rails/actions/workflows/ci.yml)
 [![Docs](https://img.shields.io/badge/docs-vsn2015.github.io-6f42c1?logo=readthedocs&logoColor=white)](https://vsn2015.github.io/concerns_on_rails)
 [![Ruby](https://img.shields.io/badge/ruby-%3E%3D%203.2-CC342D?logo=ruby&logoColor=white)](https://www.ruby-lang.org)
-[![Rails](https://img.shields.io/badge/rails-5.0--8.x-CC0000?logo=rubyonrails&logoColor=white)](https://rubyonrails.org)
+[![Rails](https://img.shields.io/badge/rails-6.0--8.1-CC0000?logo=rubyonrails&logoColor=white)](https://rubyonrails.org)
 [![License: MIT](https://img.shields.io/badge/license-MIT-3fb950.svg)](#-license)
 
 ### [📖 **Documentation**](https://vsn2015.github.io/concerns_on_rails)  ·  [💎 **RubyGems**](https://rubygems.org/gems/concerns_on_rails)  ·  [📝 **Changelog**](CHANGELOG.md)  ·  [🐛 **Issues**](https://github.com/VSN2015/concerns_on_rails/issues)
@@ -158,7 +158,7 @@ across all 43 concerns — press <kbd>/</kbd> and type.
 Add to your application's `Gemfile`:
 
 ```ruby
-gem "concerns_on_rails", "~> 1.28"
+gem "concerns_on_rails", "~> 1.29"
 ```
 
 Or pull the latest from GitHub:
@@ -200,7 +200,25 @@ still wins over the gem-wide fallback.
 ## 🧪 Compatibility
 
 - **Ruby**: 3.2+
-- **Rails**: declared 5.0 through 8.x — in practice the Ruby 3.2 requirement means Rails 7.0.4+ is what can actually install the gem; the test suite runs against Rails 7.1
+- **Rails**: 6.0 through 8.1
+
+Every one of those lines runs the full suite on every push — Rails 6.0, 6.1, 7.0, 7.1, 7.2,
+8.0 and 8.1 on SQLite, plus PostgreSQL and MySQL, and Ruby 3.3/3.4 against the current
+lines. See [`.github/workflows/ci.yml`](.github/workflows/ci.yml).
+
+**Rails 5.x is not supported**, despite what older versions of this gem declared. Rails 5
+cannot run on any Ruby this gem supports: Ruby 3 separated keyword arguments, which breaks
+Active Record 5.2's own `create_table`, and `required_ruby_version` here is `>= 3.2.0`. The
+old `>= 5.0` dependency was therefore unreachable — no bundle could ever have satisfied
+both halves of it.
+
+Two things need a Rails line newer than the 6.0 floor. Both raise or are documented where
+they apply, and nothing else in the gem is affected:
+
+| Feature | Needs | Below that |
+|---|---|---|
+| `Controllers::Sortable` — `nulls:` ordering | Rails 6.1 | Raises `ArgumentError` at macro time (Arel gained the ordering nodes in 6.1) |
+| `Models::Aliasable` — query side (`joins`/`where`/`eager_load` through an alias) | Rails 6.1 | Rails resolves a `where`-hash key to a table name, not an association, so the alias is not applied to the join. Readers, writers and `build_`/`create_` work on 6.0 |
 
 ---
 
@@ -765,7 +783,7 @@ User.find_by(email: User.normalize(:email, params[:email]))
 - `with:` takes a preset, a Proc, or an Array of them (applied in order); every entry is validated at class load.
 - `nil` values are skipped — no `nil → ""` coercion (use `:nullify_blank` for the opposite direction).
 - Preset normalizers pass non-string values through unchanged.
-- Works on Rails 5+ (no dependency on Rails 7.1's built-in `normalizes`).
+- Works on Rails 6.0+ (no dependency on Rails 7.1's built-in `normalizes`).
 
 ---
 
@@ -1429,6 +1447,10 @@ unlike Publishable/Expirable/Activatable, this one has no validators gate.
 
 ## 🪞 Aliasable
 
+> **Rails 6.1+ for the query side.** `joins` / `where` / `eager_load` through an alias
+> needs Rails to resolve a `where`-hash key to an association, which landed in 6.1. The
+> read/write side (readers, writers, `build_`/`create_`, the ids pair) works on 6.0.
+
 Alias an existing association under a second name with **full** semantics — read, write/assign, build/create, and the query side (`joins` / `includes` / `where`-hash) — not just a delegated reader. (`alias_attribute` covers columns only; Rails has no built-in association aliasing.)
 
 ```ruby
@@ -2209,7 +2231,7 @@ When several rules apply to one request the `X-RateLimit-*` headers describe the
 - The store MUST support **atomic increment-with-expiry** (`Rails.cache` with `#increment`, or Redis) — a non-atomic store under-counts under concurrency.
 - There is **no in-process default store** on purpose: the first throttled request raises `ArgumentError` until you set `throttleable_store` (or the gem-wide fallback `ConcernsOnRails.setup { |c| c.cache_store = -> { Rails.cache } }`), so you never silently rate-limit per-process.
 - When `Respondable` is included, the 429 body delegates to `render_error` (`code: "rate_limited"`).
-- Backports the essentials of Rails 7.2's `rate_limit` (with standardized headers) to Rails 5.0+. For richer rules (fail2ban, allow/deny lists, exponential backoff) reach for [`rack-attack`](https://github.com/rack/rack-attack).
+- Backports the essentials of Rails 7.2's `rate_limit` (with standardized headers) to Rails 6.0+. For richer rules (fail2ban, allow/deny lists, exponential backoff) reach for [`rack-attack`](https://github.com/rack/rack-attack).
 
 ---
 
@@ -2505,7 +2527,7 @@ Point your agent at `llms.txt` for an overview, or paste a single concern's `.md
 bundle install                                  # install dev dependencies
 bundle exec rspec                               # run the test suite (1,830 examples)
 gem build concerns_on_rails.gemspec             # build the gem
-gem install ./concerns_on_rails-1.28.9.gem      # install locally
+gem install ./concerns_on_rails-1.29.0.gem      # install locally
 
 # Preview the docs site locally (GitHub Pages serves docs/ as-is):
 cd docs && python3 -m http.server 8000          # → http://localhost:8000

data/lib/concerns_on_rails/controllers/includable.rb

@@ -130,17 +130,22 @@ module ConcernsOnRails
         return {} unless raw.respond_to?(:each_pair)
 
         allowed = self.class.includable_fields
-        # Iterate via each_pair: in a real controller `raw` is an
+        # Iterate via each_pair WITH A BLOCK: in a real controller `raw` is an
         # ActionController::Parameters, which has each_pair but no Enumerable —
         # calling each_with_object directly on it was a guaranteed
-        # NoMethodError 500 for every ?fields[...]= request.
-        raw.each_pair.with_object({}) do |(table, cols), memo|
+        # NoMethodError 500 for every ?fields[...]= request. Its block-less
+        # form is no good either: Parameters#each_pair only started returning
+        # an Enumerator in Rails 6.1, so `raw.each_pair.with_object` raised
+        # LocalJumpError ("no block given") on 6.0.
+        memo = {}
+        raw.each_pair do |table, cols|
           key = table.to_sym
           next unless allowed.key?(key)
 
           permitted = split_field_list(cols) & allowed[key]
           memo[key] = permitted unless permitted.empty?
         end
+        memo
       end
 
       private

data/lib/concerns_on_rails/models/aliasable.rb

@@ -46,6 +46,13 @@ module ConcernsOnRails
     #     must match the name you joined under (same rule as stock Rails):
     #     joins(:sections).where(sections: {...}) works,
     #     joins(:chapters).where(sections: {...}) does not.
+    #   * THE QUERY SIDE NEEDS RAILS 6.1+. Resolving a where-hash key to an
+    #     ASSOCIATION rather than to a literal table name landed in 6.1, and
+    #     that resolution is what makes Rails alias the join to the
+    #     reflection name. On 6.0 the same call emits
+    #     INNER JOIN "chapters" ... WHERE "sections"... — a reference to an
+    #     alias that was never created, which the database rejects. Readers,
+    #     writers, build_/create_ and the ids pair all work on 6.0.
     #   * The belongs_to foreign-key attribute is NOT aliased — pair with
     #     Rails' alias_attribute (e.g. :writer_id, :author_id) if needed.
     #   * has_and_belongs_to_many cannot be aliased — use has_many :through.

data/lib/concerns_on_rails/models/searchable.rb

@@ -74,7 +74,14 @@ module ConcernsOnRails
           self.searchable_case_sensitive = case_sensitive
           self.searchable_ranked = ranked
 
-          scope :search, ->(query, ranked: nil) { search_relation(query, ranked: ranked) }
+          # Options are taken POSITIONALLY, not as keywords. Rails 6.0 forwards a
+          # scope's arguments through `define_method(name) { |*args| ... }` with no
+          # `ruby2_keywords`, so under Ruby 3 a `ranked:` keyword reaches the body as
+          # a trailing positional Hash and a kwarg-taking lambda dies with
+          # `wrong number of arguments (given 2, expected 1)`. Splatting an options
+          # hash back out here behaves identically on 6.0 through 8.1 — and still
+          # raises on an unknown key, because `search_relation` names its keywords.
+          scope :search, ->(query, opts = {}) { search_relation(query, **opts) }
         end
 
         # `ranked:` nil defers to the macro's setting; true/false override it.

data/lib/concerns_on_rails/version.rb

@@ -1,3 +1,3 @@
 module ConcernsOnRails
-  VERSION = "1.28.9".freeze
+  VERSION = "1.29.0".freeze
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: concerns_on_rails
 version: !ruby/object:Gem::Version
-  version: 1.28.9
+  version: 1.29.0
 platform: ruby
 authors:
 - Ethan Nguyen
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-09-19 00:00:00.000000000 Z
+date: 2026-09-21 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: actionpack
@@ -16,7 +16,7 @@ dependencies:
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '5.0'
+        version: '6.0'
     - - "<"
       - !ruby/object:Gem::Version
         version: '9'
@@ -26,7 +26,7 @@ dependencies:
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '5.0'
+        version: '6.0'
     - - "<"
       - !ruby/object:Gem::Version
         version: '9'
@@ -36,7 +36,7 @@ dependencies:
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '5.0'
+        version: '6.0'
     - - "<"
       - !ruby/object:Gem::Version
         version: '9'
@@ -46,7 +46,7 @@ dependencies:
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '5.0'
+        version: '6.0'
     - - "<"
       - !ruby/object:Gem::Version
         version: '9'
@@ -56,7 +56,7 @@ dependencies:
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '5.0'
+        version: '6.0'
     - - "<"
       - !ruby/object:Gem::Version
         version: '9'
@@ -66,7 +66,7 @@ dependencies:
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '5.0'
+        version: '6.0'
     - - "<"
       - !ruby/object:Gem::Version
         version: '9'