sequel-activerecord_connection 2.0.0 → 2.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a2912969fb906ae413ccdded0137055b743786a4fdcf8de812c643d8c0facc6a
-  data.tar.gz: 75662cc9ae2f373a106b8c7163bc96fc4ae067a7001f39df166a780648dd9998
+  metadata.gz: 042736dc5ad00fd808dd145caa564065a11926b9bdc93698fed9a8f5b0e4aff9
+  data.tar.gz: 909816335c6b1001c605fff430bab10853c0746b2c21bd0741c4e8db58164abb
 SHA512:
-  metadata.gz: 2a2d9c7f5c1b88bb0c8285968f61ae2c8e3dd27df266df9675b14c5ff6fd9eb06a4e37a9a2c4c7638a7fe11405df2a8bfb6b79ae58dda38e8bbafcd29309b07d
-  data.tar.gz: 2e73044828506553458070cd5763ce2196706e6a58713dde428182b14f30266aa52a278dcd2a4c0e9d1b71984bb73bd8099351199140ee211c82dadbe9334985
+  metadata.gz: eb1cc2a21b801ec092e6e7b9fa7980f5a340371d72b8d4ab7afaec58f5a7eb9b2362292c9397eab2a4e6f80aa7e930b90d89cc07c617b884ac28e982bdeb7978
+  data.tar.gz: ad0b5848a8348e2566d1f1c7f51289de04aa4eba2549172c3f375f97dc06435f5bbe669426aef82ffad02cc0b0a1db63e0f76b11fdbba3bd4b021776a43ecf2a

data/CHANGELOG.md

@@ -1,3 +1,7 @@
+## 2.0.1 (2025-10-25)
+
+* Allow Active Record 8.1+ (@janko)
+
 ## 2.0.0 (2024-11-10)
 
 * The `after_commit_everywhere` gem now needs to be added to the Gemfile manually on Active Record < 7.2 (@janko)

data/README.md

@@ -27,16 +27,10 @@ an Active Record transaction, that query won't actually be executed inside a
 database transaction. This is because transactions are tied to the database
 connection; if one connection opens a transaction, this doesn't affect queries
 executed on a different connection, even if both connections are used in the
-same ruby process. With this library, transactions and queries can be
-seamlessly combined between Active Record and Sequel.
-
-In Rails context, there are additional considerations for a Sequel connection
-to play nicely. Connecting and disconnecting would have to go in lockstep with
-Active Record, to make commands such as `rails db:create` and `rails db:drop`
-work. You'd also need to find a way for system tests and the app running in the
-background to share the same database connection, which is something Sequel
-wasn't designed for. Reusing Active Record's connection means (dis)connecting
-and sharing between threads is all handled automatically.
+same ruby process.
+
+With this library, transactions and queries can be seamlessly combined between
+Active Record and Sequel.
 
 ## Installation
 

data/lib/sequel/extensions/activerecord_connection.rb

@@ -194,18 +194,12 @@ module Sequel
     # Active Record doesn't guarantee that a single connection can only be used
     # by one thread at a time, so we need to use locking, which is what Active
     # Record does internally as well.
-    if ActiveRecord.version >= Gem::Version.new("5.1")
-      def activerecord_lock
-        activerecord_connection.lock.synchronize do
-          ActiveSupport::Dependencies.interlock.permit_concurrent_loads do
-            yield
-          end
+    def activerecord_lock
+      activerecord_connection.lock.synchronize do
+        ActiveSupport::Dependencies.interlock.permit_concurrent_loads do
+          yield
         end
       end
-    else
-      def activerecord_lock
-        yield
-      end
     end
 
     def activerecord_connection

data/sequel-activerecord_connection.gemspec

@@ -1,6 +1,6 @@
 Gem::Specification.new do |spec|
   spec.name          = "sequel-activerecord_connection"
-  spec.version       = "2.0.0"
+  spec.version       = "2.0.1"
   spec.authors       = ["Janko Marohnić"]
   spec.email         = ["janko@hey.com"]
 
@@ -12,7 +12,7 @@ Gem::Specification.new do |spec|
   spec.required_ruby_version = ">= 2.5"
 
   spec.add_dependency "sequel", "~> 5.38"
-  spec.add_dependency "activerecord", ">= 5.0", "< 8.1"
+  spec.add_dependency "activerecord", ">= 5.1"
 
   spec.add_development_dependency "sequel_pg" unless RUBY_ENGINE == "jruby"
   spec.add_development_dependency "minitest"

metadata

@@ -1,14 +1,13 @@
 --- !ruby/object:Gem::Specification
 name: sequel-activerecord_connection
 version: !ruby/object:Gem::Version
-  version: 2.0.0
+  version: 2.0.1
 platform: ruby
 authors:
 - Janko Marohnić
-autorequire:
 bindir: bin
 cert_chain: []
-date: 2024-11-10 00:00:00.000000000 Z
+date: 1980-01-02 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: sequel
@@ -30,20 +29,14 @@ dependencies:
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '5.0'
-    - - "<"
-      - !ruby/object:Gem::Version
-        version: '8.1'
+        version: '5.1'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '5.0'
-    - - "<"
-      - !ruby/object:Gem::Version
-        version: '8.1'
+        version: '5.1'
 - !ruby/object:Gem::Dependency
   name: sequel_pg
   requirement: !ruby/object:Gem::Requirement
@@ -109,7 +102,6 @@ homepage: https://github.com/janko/sequel-activerecord_connection
 licenses:
 - MIT
 metadata: {}
-post_install_message:
 rdoc_options: []
 require_paths:
 - lib
@@ -124,8 +116,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.5.11
-signing_key:
+rubygems_version: 3.6.9
 specification_version: 4
 summary: Allows Sequel to use ActiveRecord connection for database interaction.
 test_files: []