Skip to content

Release 0.3.0: require ActiveRecord 8.1 - #39

Merged
anthonyoconnorclio merged 2 commits into
masterfrom
remove-ar-7-appraisals
Nov 2, 2026
Merged

anthonyoconnorclio merged 2 commits into
masterfrom
remove-ar-7-appraisals

Conversation

@anthonyoconnorclio

@anthonyoconnorclio anthonyoconnorclio commented Nov 2, 2026 •

Copy link
Copy Markdown
Contributor

Why

Overlord shows the only Clio consumer of this gem is clio/themis, which runs ActiveRecord 8.1.4. CI only tested AR 7.0 and 7.1, so we had no signal the gem works on the version we actually ship.

Running the suite on 8.1 confirmed the gap: the spec setup couldn't boot at all. ActiveRecord::MigrationContext.new stopped accepting the SchemaMigration class as its second argument in Rails 7.2. Passing only the migrations path lets it pick the schema migration from the connection. The gem code itself needed no changes; all 20 specs pass on 8.1.

Since CI now only verifies 8.1, this also releases 0.3.0 marked as 8.1-only, so we don't publish a version that claims support we no longer test:

  • activerecord >= 8.1 is now a runtime dependency (it was only a development dependency before), so RubyGems will stop apps on older Rails from resolving to 0.3.0 rather than relying on users reading the README.
  • Minor bump because dropping supported Rails versions is breaking for a pre-1.0 gem.
  • 0.2.3 was never published to RubyGems. Library code is unchanged since v0.2.2, so the README now points ActiveRecord 6.1–8.0 users at v0.2.2.

Dropping the 7.0 appraisal also removes the sqlite3 ~> 1.4 and concurrent-ruby 1.3.4 pins that only existed to keep the old AR 7.0 SQLite adapter loading.

Releasing

Publishing is triggered by the gem-push workflow when a GitHub release is published. After merge, create a release with tag v0.3.0 on master.

For reviewers

  • gemfiles/ is gitignored, so the generated appraisal gemfiles aren't part of this diff; CI runs appraisal install to generate them.

The only Clio consumer of this gem (themis) runs ActiveRecord 8.1, but CI
only exercised 7.0 and 7.1, so we had no signal that the gem works on the
version we actually ship. Running the suite on 8.1 immediately surfaced a
break in the spec setup: MigrationContext no longer accepts the
SchemaMigration class as its second argument (removed in 7.2), so the
suite could not boot. Letting it pick the schema migration from the
connection works on 7.1+.

Dropping the 7.0 appraisal also removes the sqlite3 1.x and
concurrent-ruby pins that only existed to keep that old adapter loading.
CI now only verifies ActiveRecord 8.1, so publishing a version that still
claims 7.0+ support would promise compatibility we no longer test.
Declaring activerecord as a runtime dependency lets RubyGems stop apps on
older Rails from resolving to this version, instead of relying on users
reading the README.

This is a minor bump because dropping supported Rails versions is a
breaking change for a pre-1.0 gem. 0.2.3 was never published, so 7.x
users stay on 0.2.2, which has the same library code.
@anthonyoconnorclio anthonyoconnorclio changed the title Test against ActiveRecord 8.1 instead of 7.0/7.1 Release 0.3.0: require ActiveRecord 8.1 Nov 2, 2026
@anthonyoconnorclio
anthonyoconnorclio marked this pull request as ready for review November 2, 2026 22:26
@anthonyoconnorclio
anthonyoconnorclio requested a review from a team as a code owner November 2, 2026 22:26

@hype08 hype08 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@anthonyoconnorclio
anthonyoconnorclio merged commit 9ca64ea into master Nov 2, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants