studio-engine 0.10.0 → 0.11.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 20b0e58f17421ce741452b329000bc657f0dba0304198d7dc1fb59cb448bfc6d
-  data.tar.gz: d4446a5bad4b0b744e54ad7d4f275cf77455a68f2cf3289d6d9c472ca1f3c548
+  metadata.gz: 4d4a633071c04010dadfb92d3beef1a7e075a90c94e55ab5761a03a114f48f40
+  data.tar.gz: fc17d48b30cfcbde79e4c3bdc5bf618789a7765dbc359a134b28800cc772429e
 SHA512:
-  metadata.gz: b15b1f884815e8afbad3d9aa181589230193942970d62457075d08c47521c967a005025560e665b436ceb8a6c78f425688430f122cad9a7f21e8a4432bd4ca22
-  data.tar.gz: 5a6c6817018309298bb3a8eb686f61d7e93d9718d5b8ce5b5a8e642efc82f99695d6bf0c4f23b9421fa8c65481722e9164934c7cbe47f254e3abb482d7ea42ed
+  metadata.gz: e32e14a996202c61dd230a4084927539618341c0343bbafad1066280394da6d84976222a5621000157d6e84df83452c6a5f234f36ca11e18c408e340757a0b49
+  data.tar.gz: 8592453e2efdbad7c3df75bfb13274a6abfa080f9de9e6188a70d90e935d2dfa1446c788f15d55eab467207bcfa9cef129bf9b0abf3fbb001e846a11a6c31f3f

data/CHANGELOG.md

@@ -4,6 +4,32 @@ The format is [Keep a Changelog](https://keepachangelog.com/en/1.1.0/). This pro
 
 ## Unreleased
 
+## 0.11.0 — 2026-06-24
+
+### Changed
+- **Rails 8.1 support** — widened the gemspec `rails` bound from
+  `">= 7.0", "< 8.0"` to `">= 7.2", "< 8.2"`, so consuming apps can migrate to
+  Rails 8.1 independently (the engine no longer pins the ecosystem to Rails 7).
+  This release is the gate for the McRitchie Rails 8.1 train — `mcritchie-studio`
+  and `turf-monster` can bundle Rails 8.1 only once this version is published.
+  The lower bound moves to 7.2 (the oldest Rails the apps actually run) since
+  Rails 8 requires Ruby >= 3.2 and the ecosystem is already on Ruby 3.3.11.
+
+### Added
+- **`test/dummy` Rails app + `test/integration/engine_rails_8_1_boot_test.rb`** —
+  boots the engine inside a real Rails app and exercises its Rails-version-
+  sensitive surfaces (the Railtie registration, Zeitwerk autoload wiring, the
+  `Studio.routes` DSL, and the `ErrorLog` / `ThemeSetting` / `Sluggable`
+  ActiveRecord models). Re-run this against any new Rails line before widening
+  the bound again. The engine's full unit suite + this boot test are green
+  against Rails 8.1.3 (ActiveSupport/ActiveRecord 8.1, Zeitwerk 2.8, minitest 6).
+
+### Fixed
+- `bin/release-check` now prefers the `ruby@3.3` toolchain (was pinned to the
+  retired `ruby@3.1`, which cannot resolve Rails 8.1) and runs the full test
+  list, including the new Rails 8.1 boot test and the previously-omitted
+  `link_token` / sticky-header / admin-models-table tests.
+
 ## 0.10.0 — 2026-06-24
 
 ### Added

data/Gemfile

@@ -2,17 +2,19 @@ source "https://rubygems.org"
 
 gemspec
 
-# nokogiri 1.18.10 has 3 CVEs (1 HIGH regex-backtracking + 2 MEDIUM
-# in XSLT / xmlC14NExecute). Fix is `>= 1.19.3` but nokogiri 1.19.x
-# requires Ruby 3.2+. The ecosystem currently runs on Ruby 3.1.7;
-# bumping Ruby is a separate effort (across both Rails apps).
-#
-# **Important**: this gem does NOT declare nokogiri as a runtime
-# dependency in its gemspec — nokogiri comes into the consuming
-# Rails app via Rails itself. Consumers running Rails on a Ruby
-# version that supports nokogiri 1.19.x will resolve it. The
-# studio-engine gem's own Gemfile.lock (this repo's dev env) is the
-# only place still on 1.18.10.
-#
-# Tracked in SECURITY-AUDIT-2026-05-17.md. When the ecosystem bumps
-# to Ruby 3.2+, add: gem "nokogiri", ">= 1.19.3", group: :development
+# nokogiri: historically pinned to 1.18.10 here while the ecosystem was on
+# Ruby 3.1.7 (nokogiri >= 1.19.x requires Ruby 3.2+). The ecosystem is now on
+# Ruby 3.3.11, so a plain `bundle update` resolves the patched nokogiri
+# (>= 1.19.3, the line that fixed 3 CVEs: 1 HIGH regex-backtracking + 2 MEDIUM
+# XSLT / xmlC14NExecute). This gem still does NOT declare nokogiri as a runtime
+# dependency — it arrives via Rails in the consuming app. Tracked in
+# SECURITY-AUDIT-2026-05-17.md.
+
+group :development, :test do
+  # SQLite drives the test/dummy Rails app's in-memory database (see
+  # test/integration/engine_rails_8_1_boot_test.rb), which boots the engine
+  # against a real Rails app so we catch Rails-version incompatibilities in the
+  # engine's ActiveRecord/Railtie surfaces. Not a runtime dependency — the
+  # consuming apps bring their own database adapter. Rails 8.1 needs sqlite3 ~> 2.1.
+  gem "sqlite3", ">= 2.1"
+end

data/lib/studio/version.rb

@@ -1,3 +1,3 @@
 module Studio
-  VERSION = "0.10.0"
+  VERSION = "0.11.0"
 end

data/studio-engine.gemspec

@@ -21,7 +21,7 @@ Gem::Specification.new do |spec|
   spec.files = Dir["lib/**/*", "app/**/*", "config/**/*", "db/**/*", "tailwind/**/*", "Gemfile", "studio-engine.gemspec", "README.md", "CHANGELOG.md", "LICENSE"]
   spec.require_paths = ["lib"]
 
-  spec.add_dependency "rails", ">= 7.0", "< 8.0"
+  spec.add_dependency "rails", ">= 7.2", "< 8.2"
   spec.add_dependency "tailwindcss-rails", "~> 4.5"
   spec.add_dependency "faker", ">= 2.0", "< 4.0"
   spec.add_dependency "solid_queue", ">= 1.0", "< 2.0"

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: studio-engine
 version: !ruby/object:Gem::Version
-  version: 0.10.0
+  version: 0.11.0
 platform: ruby
 authors:
 - Alex McRitchie
@@ -15,20 +15,20 @@ dependencies:
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '7.0'
+        version: '7.2'
     - - "<"
       - !ruby/object:Gem::Version
-        version: '8.0'
+        version: '8.2'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '7.0'
+        version: '7.2'
     - - "<"
       - !ruby/object:Gem::Version
-        version: '8.0'
+        version: '8.2'
 - !ruby/object:Gem::Dependency
   name: tailwindcss-rails
   requirement: !ruby/object:Gem::Requirement