familia 2.1.0 → 2.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: e83013bddd8ff985ad1cd9ef73421146b5fea6c35cbb77aa0cf12656dd270f68
-  data.tar.gz: ba7ebef4af806d823317fd41e1875733b12971b3c6321e841c9ecbf0c9d727a0
+  metadata.gz: 923e4c76b9ee95ca39160a66ec9534462b21b16e273fc27c6e67e707647da1a4
+  data.tar.gz: c8dd58304412dd4d9ad57727a4044d8680c16f701869e3f8dd7d0e2a57ed221a
 SHA512:
-  metadata.gz: 126d79d60cad6c4ed4ed03a557f4435aec82d03ef2230ad64e4d2205f8c8856cc74b140c18fb5f1d567631f203f6b259e7d19d0bed8f36e09b5540fc004f4e6d
-  data.tar.gz: cb5a52b4622c9f193d3858b0f2766795f49000f56fccbffdc630dc5b05e68db0a8c200ad25137bf543d9fc64ee2f53cab891517a5d9f91c2dd8debeb2119b7e7
+  metadata.gz: 0716f0b0e47a4758933547b884da5265ce186ce3eba55def7672e2540823b8f15671791ed7b2906f6862d863faa273436fb9e52434cec0e10a91a9bd7614ae9e
+  data.tar.gz: 6e018ee75bb16fa2e1be7a7e812dbcd8d8ca9e8a3c82fe078ef19958e3736f01f8c5f34b925a9fc6a0fd3d7ca709604571a5915ee2b828f2a67539e61ac401a2

data/CHANGELOG.rst

@@ -7,6 +7,43 @@ The format is based on `Keep a Changelog <https://keepachangelog.com/en/1.1.0/>`
 
    <!--scriv-insert-here-->
 
+.. _changelog-2.1.1:
+
+2.1.1 — 2026-02-02
+==================
+
+Added
+-----
+
+- Added ``serialization_consistency_try.rb`` regression tests verifying that
+  object-based lookups work consistently across relationships module and direct
+  DataType access for sorted sets, unsorted sets, and lists.
+
+Fixed
+-----
+
+- Fixed serialization mismatch in relationships module where extracting
+  ``.identifier`` before passing to DataType methods caused cross-path lookup
+  failures. Items added via relationships couldn't be found via direct DataType
+  access because ``serialize_value(object)`` extracts raw identifiers while
+  ``serialize_value(string)`` JSON-encodes them. Now passes Familia objects
+  directly to DataType methods. (`#212 <https://github.com/delano/familia/issues/212>`_)
+
+Documentation
+-------------
+
+- Documented known limitation: string identifier lookups get JSON-encoded by
+  design. Always use Familia objects instead of raw string identifiers for
+  DataType operations like ``member?()``, ``score()``, and ``remove()``.
+
+AI Assistance
+-------------
+
+- Claude assisted with root cause analysis of the serialization mismatch,
+  identifying the 7 occurrences in ``collection_operations.rb`` where
+  ``.identifier`` extraction needed to be removed, and writing comprehensive
+  regression tests covering all three collection types.
+
 .. _changelog-2.1.0:
 
 2.1.0 — 2026-02-01

data/Gemfile.lock

@@ -1,9 +1,9 @@
 PATH
   remote: .
   specs:
-    familia (2.1.0)
+    familia (2.1.1)
       concurrent-ruby (~> 1.3)
-      connection_pool (~> 2.5)
+      connection_pool (>= 2.4, < 4.0)
       csv (~> 3.3)
       logger (~> 1.7)
       oj (~> 3.16)
@@ -19,7 +19,7 @@ GEM
     benchmark (0.5.0)
     bigdecimal (3.3.1)
     concurrent-ruby (1.3.6)
-    connection_pool (2.5.5)
+    connection_pool (3.0.2)
     csv (3.3.5)
     date (3.5.0)
     debug (1.11.0)

data/examples/relationships.rb

@@ -186,7 +186,7 @@ domain1.remove_from_customer_domains(customer)
 puts "✓ Removed #{domain1.name} from customer domains"
 
 # Remove from tracking collections
-Domain.active_domains.remove(domain2.identifier)
+Domain.active_domains.remove(domain2)
 puts "✓ Removed #{domain2.name} from active domains"
 
 # Verify cleanup

data/familia.gemspec

@@ -20,7 +20,7 @@ Gem::Specification.new do |spec|
   spec.required_ruby_version = Gem::Requirement.new('>= 3.2')
 
   spec.add_dependency 'concurrent-ruby', '~> 1.3'
-  spec.add_dependency 'connection_pool', '~> 2.5'
+  spec.add_dependency 'connection_pool', '>= 2.4', '< 4.0'
   spec.add_dependency 'csv', '~> 3.3'
   spec.add_dependency 'logger', '~> 1.7'
   spec.add_dependency 'oj', '~> 3.16'

data/lib/familia/features/relationships/collection_operations.rb

@@ -31,13 +31,13 @@ module Familia
           when :sorted_set
             # Ensure score is never nil for sorted sets
             score ||= calculate_item_score(item, target_class, collection_name)
-            collection.add(item.identifier, score)
+            collection.add(item, score)
           when :list
             # Lists use push/unshift operations
-            collection.add(item.identifier)
+            collection.add(item)
           when :set
             # Sets use simple add
-            collection.add(item.identifier)
+            collection.add(item)
           else
             raise ArgumentError, "Unknown collection type: #{type}"
           end
@@ -49,7 +49,7 @@ module Familia
         # @param type [Symbol] Collection type
         def remove_from_collection(collection, item, type: nil)
           # All collection types support remove/delete
-          collection.remove(item.identifier)
+          collection.remove(item)
         end
 
         # Check if an item is a member of a collection
@@ -57,7 +57,7 @@ module Familia
         # @param item [Object] The item to check (must respond to identifier)
         # @return [Boolean] True if item is in collection
         def member_of_collection?(collection, item)
-          collection.member?(item.identifier)
+          collection.member?(item)
         end
 
         # Bulk add items to a collection using DataType methods
@@ -72,12 +72,12 @@ module Familia
             # Add items one by one for sorted sets to ensure proper scoring
             items.each do |item|
               score = calculate_item_score(item, target_class, collection_name)
-              collection.add(item.identifier, score)
+              collection.add(item, score)
             end
           when :set, :list
             # For sets and lists, add items one by one using DataType methods
             items.each do |item|
-              collection.add(item.identifier)
+              collection.add(item)
             end
           else
             raise ArgumentError, "Unknown collection type: #{type}"

data/lib/familia/features/relationships/indexing/rebuild_strategies.rb

@@ -401,7 +401,7 @@ module Familia
                 collection_name = participation.collection_name
                 scope_collection = scope_instance.send(collection_name)
                 # Filter to only objects that belong to this scope
-                objects = objects.select { |obj| scope_collection.member?(obj.identifier) }
+                objects = objects.select { |obj| scope_collection.member?(obj) }
               end
             end
 

data/lib/familia/features/relationships/participation/participant_methods.rb

@@ -29,7 +29,7 @@ module Familia
         # └── position_in_employee_domains(employee)      # Get my position (list only)
         #
         # Note: To update scores, use the DataType API directly:
-        #   employee.domains.add(domain.identifier, new_score, xx: true)
+        #   employee.domains.add(domain, new_score, xx: true)
         #
         module Builder
           extend CollectionOperations
@@ -296,7 +296,7 @@ module Familia
           # Creates: domain.score_in_customer_domains(customer)
           #
           # Note: Score updates use DataType API directly:
-          #   customer.domains.add(domain.identifier, new_score, xx: true)
+          #   customer.domains.add(domain, new_score, xx: true)
           def self.build_score_methods(participant_class, target_name, collection_name)
             # Get score method
             score_method = "score_in_#{target_name}_#{collection_name}"
@@ -305,7 +305,9 @@ module Familia
 
               # Use Horreum's DataType accessor instead of manual key construction
               collection = target_instance.send(collection_name)
-              collection.score(identifier)
+              # Pass self (Familia object) not identifier (string) for correct serialization
+              # See GitHub issue #212: serialize_value handles objects vs strings differently
+              collection.score(self)
             end
           end
 

data/lib/familia/features/relationships/participation.rb

@@ -691,14 +691,18 @@ module Familia
 
                 case config.type
                 when :sorted_set
-                  score = collection.score(identifier)
+                  # Pass self (Familia object) not identifier (string) for correct serialization
+                  # See GitHub issue #212: serialize_value handles objects vs strings differently
+                  score = collection.score(self)
                   next unless score
 
                   decoded_score = decode_score(score) if respond_to?(:decode_score)
                 when :set
-                  is_member = collection.member?(identifier)
+                  # Pass self (Familia object) not identifier (string) for correct serialization
+                  is_member = collection.member?(self)
                   next unless is_member
                 when :list
+                  # List uses to_a which returns deserialized values, so identifier is correct here
                   position = collection.to_a.index(identifier)
                   next unless position
                 end

data/lib/familia/version.rb

@@ -4,5 +4,5 @@
 
 module Familia
   # Version information for the Familia
-  VERSION = '2.1.0' unless defined?(Familia::VERSION)
+  VERSION = '2.1.1' unless defined?(Familia::VERSION)
 end

data/try/features/relationships/participation_reverse_methods_try.rb

@@ -210,8 +210,9 @@ user1_team_ids.include?(@team1.identifier)
 #=> true
 
 ## Test multiple users in same team - add user2
+# Use object, not string identifier, for correct serialization (see issue #212)
 @team1.add_members_instance(@user2)
-@team1.members.member?(@user2.identifier)
+@team1.members.member?(@user2)
 #=> true
 
 ## Test team1 now has two members

data/try/features/relationships/participation_target_class_resolution_try.rb

@@ -94,8 +94,9 @@ end
 
 ## Test Symbol target class resolution works
 # This is the primary regression test - it should not raise NoMethodError
+# Use object, not string identifier, for correct serialization (see issue #212)
 @customer.add_domains_instance(@domain)
-@customer.domains.member?(@domain.identifier)
+@customer.domains.member?(@domain)
 #=> true
 
 ## Test domain bidirectional methods were created correctly
@@ -109,7 +110,7 @@ end
 ## Test domain can add itself using generated method
 @customer.domains.remove(@domain)
 @domain.add_to_symbol_resolution_customer_domains(@customer)
-@customer.domains.member?(@domain.identifier)
+@customer.domains.member?(@domain)
 #=> true
 
 ## Test domain score calculation works with Symbol target class
@@ -124,7 +125,7 @@ end
 ## Test String target class resolution works
 # This is the secondary regression test
 @customer.add_tags_instance(@tag)
-@customer.tags.member?(@tag.identifier)
+@customer.tags.member?(@tag)
 #=> true
 
 ## Test tag bidirectional methods were created correctly
@@ -138,7 +139,7 @@ end
 ## Test tag can add itself using generated method
 @customer.tags.remove(@tag)
 @tag.add_to_symbol_resolution_customer_tags(@customer)
-@customer.tags.member?(@tag.identifier)
+@customer.tags.member?(@tag)
 #=> true
 
 ## Test tag membership check works with String target class (sets don't have scores)

data/try/features/relationships/relationships_api_changes_try.rb

@@ -123,23 +123,24 @@ ApiTestUser.all_users.class.name
 
 ## Automatic tracking addition works on save
 @user.save
-ApiTestUser.all_users.member?(@user.identifier)
+ApiTestUser.all_users.member?(@user)
 #=> true
 
 ## Score calculation works for simple field scores
-score = ApiTestUser.all_users.score(@user.identifier)
+# Use object, not string identifier, for correct serialization (see issue #212)
+score = ApiTestUser.all_users.score(@user)
 score.is_a?(Float) && score > 0
 #=> true
 
 ## Score calculation works for lambda scores with active user
 ApiTestUser.add_to_active_users(@user)  # Explicit addition to active_users collection
-active_score = ApiTestUser.active_users.score(@user.identifier)
+active_score = ApiTestUser.active_users.score(@user)
 active_score > 0
 #=> true
 
 ## Score calculation works for lambda scores with inactive user
 ApiTestUser.add_to_active_users(@inactive_user)  # Explicit addition to active_users collection
-ApiTestUser.active_users.member?(@inactive_user.identifier)
+ApiTestUser.active_users.member?(@inactive_user)
 #=> true
 
 # =============================================
@@ -285,7 +286,8 @@ membership_meta.scope_class
 
 ## Class tracking and indexing work together automatically on save
 @user.save  # Should automatically update both tracking and indexing
-ApiTestUser.all_users.member?(@user.identifier) && ApiTestUser.email_lookup.get(@user.email) == @user.user_id
+# Use object for member?, not string identifier (see issue #212)
+ApiTestUser.all_users.member?(@user) && ApiTestUser.email_lookup.get(@user.email) == @user.user_id
 #=> true
 
 ## Parent-based relationships work with tracking

data/try/features/relationships/serialization_consistency_try.rb

@@ -0,0 +1,292 @@
+# try/features/relationships/serialization_consistency_try.rb
+#
+# frozen_string_literal: true
+
+# Regression tests for GitHub issue #212: Serialization mismatch in collection_operations.rb
+#
+# BUG SUMMARY:
+# The relationships module was extracting `.identifier` before passing to DataType methods.
+# The serialize_value method handles Familia objects differently from raw strings:
+#
+#   serialize_value(familia_object) => extracts identifier (raw string): "id123"
+#   serialize_value("id123")        => JSON encodes (adds quotes): "\"id123\""
+#
+# This causes cross-path inconsistencies when data added via relationships module
+# cannot be found via DataType methods using string identifiers, and vice versa.
+#
+# FIX APPLIED (collection_operations.rb + participant_methods.rb):
+# Pass the full Familia object to DataType methods instead of extracting the identifier
+# first. Let serialize_value handle the object correctly. This ensures:
+#   - add(item) stores raw identifier
+#   - remove(item) removes raw identifier
+#   - member?(item) finds raw identifier
+#   - score(item) queries with raw identifier
+#
+# TEST STRUCTURE:
+# 1. Tests verify that issue #212 is fixed - object-based lookups work across paths
+# 2. Tests marked "KNOWN LIMITATION" document that string identifier lookups get
+#    JSON-encoded, causing mismatches. This is by design - always use Familia
+#    objects instead of raw string identifiers for DataType operations.
+
+require_relative '../../support/helpers/test_helpers'
+
+# Test classes for serialization consistency testing
+class SerConsistencyOwner < Familia::Horreum
+  feature :relationships
+
+  identifier_field :owner_id
+  field :owner_id
+  field :name
+
+  # All three collection types to test
+  sorted_set :members_zset
+  set :members_set
+  list :members_list
+end
+
+class SerConsistencyMember < Familia::Horreum
+  feature :relationships
+
+  identifier_field :member_id
+  field :member_id
+  field :email
+  field :created_at
+
+  # Participates in all three collection types
+  participates_in SerConsistencyOwner, :members_zset, score: :created_at, type: :sorted_set
+  participates_in SerConsistencyOwner, :members_set, type: :set
+  participates_in SerConsistencyOwner, :members_list, type: :list
+end
+
+@owner = SerConsistencyOwner.new(owner_id: 'owner-abc123', name: 'Test Owner')
+@member1 = SerConsistencyMember.new(
+  member_id: 'member-def456',
+  email: 'member1@example.com',
+  created_at: Familia.now.to_i
+)
+@member2 = SerConsistencyMember.new(
+  member_id: 'member-ghi789',
+  email: 'member2@example.com',
+  created_at: (Familia.now + 100).to_i
+)
+@owner.save
+@member1.save
+@member2.save
+
+# =============================================================================
+# 1. SORTED SET (zset) - Cross-Path Consistency
+# =============================================================================
+
+## Add via relationships module, verify raw identifier is stored correctly
+@member1.add_to_ser_consistency_owner_members_zset(@owner)
+@owner.members_zset.membersraw.include?('member-def456')
+#=> true
+
+## Add via relationships module, lookup via DataType.member? with object
+@owner.members_zset.member?(@member1)
+#=> true
+
+## KNOWN LIMITATION: DataType.member? with string identifier
+# After add via relationships, lookup with raw string identifier.
+# Currently fails: serialize_value("member-def456") => "\"member-def456\""
+# but stored value is "member-def456" (raw, no quotes).
+# This is documented behavior - use objects instead of string identifiers.
+@owner.members_zset.member?(@member1.member_id)
+#=> false
+
+## Score retrieval: relationships module matches DataType with object
+@rel_score = @member1.score_in_ser_consistency_owner_members_zset(@owner)
+@dt_score = @owner.members_zset.score(@member1)
+@rel_score == @dt_score && @rel_score.is_a?(Float)
+#=> true
+
+## KNOWN LIMITATION: Score retrieval via DataType with string identifier
+# Same serialization asymmetry: score("member-def456") queries for wrong value.
+# Returns nil because the JSON-encoded string doesn't match the stored raw identifier.
+@dt_score_str = @owner.members_zset.score(@member1.member_id)
+@dt_score_str.nil?
+#=> true
+
+## Remove via relationships module, verify removed
+@member1.remove_from_ser_consistency_owner_members_zset(@owner)
+@owner.members_zset.member?(@member1)
+#=> false
+
+## Add via DataType directly with object, lookup via relationships module
+@owner.members_zset.add(@member2, 200.0)
+@member2.in_ser_consistency_owner_members_zset?(@owner)
+#=> true
+
+## KNOWN LIMITATION: DataType add + DataType string lookup
+# When added via DataType.add(object), stored as raw identifier.
+# DataType.member?(string) still JSON-encodes, causing mismatch.
+# Use objects instead of string identifiers.
+@owner.members_zset.member?(@member2.member_id)
+#=> false
+
+## Remove via DataType, verify removed via relationships module
+@owner.members_zset.remove(@member2)
+@member2.in_ser_consistency_owner_members_zset?(@owner)
+#=> false
+
+# =============================================================================
+# 2. UNSORTED SET - Cross-Path Consistency
+# =============================================================================
+
+## Add via relationships module to unsorted set
+@member1.add_to_ser_consistency_owner_members_set(@owner)
+@owner.members_set.member?(@member1)
+#=> true
+
+## KNOWN LIMITATION: Unsorted set string identifier lookup
+# Use objects instead of string identifiers.
+@owner.members_set.member?(@member1.member_id)
+#=> false
+
+## Verify raw identifier storage in unsorted set
+@owner.members_set.membersraw.include?('member-def456')
+#=> true
+
+## Remove from unsorted set via relationships module
+@member1.remove_from_ser_consistency_owner_members_set(@owner)
+@owner.members_set.member?(@member1)
+#=> false
+
+## Add via DataType to unsorted set, lookup via relationships module
+@owner.members_set.add(@member2)
+@member2.in_ser_consistency_owner_members_set?(@owner)
+#=> true
+
+## Clean up unsorted set
+@owner.members_set.remove(@member2)
+@member2.in_ser_consistency_owner_members_set?(@owner)
+#=> false
+
+# =============================================================================
+# 3. LIST - Cross-Path Consistency
+# =============================================================================
+
+## Add via relationships module to list
+@member1.add_to_ser_consistency_owner_members_list(@owner)
+@owner.members_list.member?(@member1)
+#=> true
+
+## KNOWN LIMITATION: List string identifier lookup
+# Use objects instead of string identifiers.
+@owner.members_list.member?(@member1.member_id)
+#=> false
+
+## Verify raw identifier storage in list
+@owner.members_list.membersraw.include?('member-def456')
+#=> true
+
+## Remove from list via relationships module
+@member1.remove_from_ser_consistency_owner_members_list(@owner)
+@owner.members_list.member?(@member1)
+#=> false
+
+## Add via DataType to list, lookup via relationships module
+@owner.members_list.add(@member2)
+@member2.in_ser_consistency_owner_members_list?(@owner)
+#=> true
+
+## Clean up list
+@owner.members_list.remove(@member2)
+@member2.in_ser_consistency_owner_members_list?(@owner)
+#=> false
+
+# =============================================================================
+# 4. SERIALIZATION CONSISTENCY VERIFICATION
+# =============================================================================
+
+## Serialization of Familia object extracts raw identifier (no JSON encoding)
+@owner.members_zset.send(:serialize_value, @member1)
+#=> "member-def456"
+
+## Serialization of raw string JSON-encodes it (adds quotes)
+@owner.members_zset.send(:serialize_value, "member-def456")
+#=> "\"member-def456\""
+
+## Object lookup works, string lookup is a known limitation
+# Add using object stores raw identifier
+@owner.members_zset.add(@member1, 100.0)
+# Object lookup works; string lookup returns false (known limitation)
+@obj_lookup = @owner.members_zset.member?(@member1)
+@str_lookup = @owner.members_zset.member?(@member1.member_id)
+[@obj_lookup, @str_lookup]
+#=> [true, false]
+
+## Clean up after serialization verification
+@owner.members_zset.remove(@member1)
+@owner.members_zset.member?(@member1)
+#=> false
+
+# =============================================================================
+# 5. ROUND-TRIP CONSISTENCY (ADD + REMOVE via mixed paths)
+# =============================================================================
+
+## Add via relationships, remove via DataType (sorted_set)
+@member1.add_to_ser_consistency_owner_members_zset(@owner)
+@owner.members_zset.remove(@member1)
+@member1.in_ser_consistency_owner_members_zset?(@owner)
+#=> false
+
+## Add via DataType, remove via relationships (sorted_set)
+@owner.members_zset.add(@member1, 100.0)
+@member1.remove_from_ser_consistency_owner_members_zset(@owner)
+@owner.members_zset.member?(@member1)
+#=> false
+
+## KNOWN LIMITATION: Remove via DataType using string identifier
+# Add via relationships stores raw identifier, remove with string fails
+# because remove("id") serializes to "\"id\"" which doesn't match stored "id".
+# Use objects instead of string identifiers.
+@member2.add_to_ser_consistency_owner_members_zset(@owner)
+@owner.members_zset.remove(@member2.member_id)  # This won't actually remove it
+@member2.in_ser_consistency_owner_members_zset?(@owner)
+#=> true
+
+## Add via relationships, remove via DataType (unsorted set)
+@member1.add_to_ser_consistency_owner_members_set(@owner)
+@owner.members_set.remove(@member1)
+@member1.in_ser_consistency_owner_members_set?(@owner)
+#=> false
+
+## Add via DataType, remove via relationships (unsorted set)
+@owner.members_set.add(@member1)
+@member1.remove_from_ser_consistency_owner_members_set(@owner)
+@owner.members_set.member?(@member1)
+#=> false
+
+## Add via relationships, remove via DataType (list)
+@member1.add_to_ser_consistency_owner_members_list(@owner)
+@owner.members_list.remove(@member1)
+@member1.in_ser_consistency_owner_members_list?(@owner)
+#=> false
+
+## Add via DataType, remove via relationships (list)
+@owner.members_list.add(@member1)
+@member1.remove_from_ser_consistency_owner_members_list(@owner)
+@owner.members_list.member?(@member1)
+#=> false
+
+# =============================================================================
+# CLEANUP
+# =============================================================================
+
+## Clean up all test data
+begin
+  # Clean up collections first
+  @owner.members_zset.delete!
+  @owner.members_set.delete!
+  @owner.members_list.delete!
+  # Then destroy objects
+  [@owner, @member1, @member2].each do |obj|
+    obj.destroy if obj.respond_to?(:destroy) && obj.exists?
+  end
+  true
+rescue => e
+  puts "Cleanup warning: #{e.message}"
+  false
+end
+#=> true

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: familia
 version: !ruby/object:Gem::Version
-  version: 2.1.0
+  version: 2.1.1
 platform: ruby
 authors:
 - Delano Mandelbaum
@@ -27,16 +27,22 @@ dependencies:
   name: connection_pool
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '2.4'
+    - - "<"
       - !ruby/object:Gem::Version
-        version: '2.5'
+        version: '4.0'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '2.4'
+    - - "<"
       - !ruby/object:Gem::Version
-        version: '2.5'
+        version: '4.0'
 - !ruby/object:Gem::Dependency
   name: csv
   requirement: !ruby/object:Gem::Requirement
@@ -390,6 +396,7 @@ files:
 - try/features/relationships/relationships_performance_try.rb
 - try/features/relationships/relationships_performance_working_try.rb
 - try/features/relationships/relationships_try.rb
+- try/features/relationships/serialization_consistency_try.rb
 - try/features/safe_dump/safe_dump_advanced_try.rb
 - try/features/safe_dump/safe_dump_try.rb
 - try/features/schema_registry_try.rb
@@ -582,7 +589,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.7.2
+rubygems_version: 3.6.9
 specification_version: 4
 summary: An ORM for Valkey-compatible databases in Ruby.
 test_files: []