- Delegate CollectionProxy#bitemporal_value to Relation #168
- Fix unintended valid_datetime set when
CollectionProxy#load#169
- Fix a typo #157
- Remove unneeded unscope values #159
- Remove unused
without_ignoreoption #160 - update auto assign #161
- Support date type of valid time #149
- Add support Rails 7.1 #151
- Add Persistence#bitemporal_at and ActiveRecord::Bitemporal.bitemporal_at #152
- Change not to create history when destroying with
force_update#135 - Raise
ValidDatetimeRangeErrorinstead ofRecordInvalidin_update_row#136
- [proposal]When bitemporal_at exists inside the nest, the specified date was not prioritized, so the date of the inner bitemporal_at is now prioritized. #121
- Drop support Rails 5.2 #122
- Add required_ruby_version >= 2.7.0 #125
-
Add support
bitemporal_callbacks#123class Employee < ActiveRecord::Base include ActiveRecord::Bitemporal after_bitemporal_create :log_create after_bitemporal_update :log_update after_bitemporal_destroy :log_destroy private def log_create puts "employee created" end def log_update puts "employee updated" end def log_destroy puts "employee destroyed" end end employee = Employee.create!(...) # => "employee created" employee.update!(...) # => "employee updated" employee.destroy! # => "employee destroyed"
- Remove Gemfile.lock #126
- Remove test cases for using bitemporal_option_merge! of ActiveRecord:::Bitemporal::Callbacks #129
- replace postgres docker image
- use Matrix Jobs in CircleCI
- Add support changing swapped_id, when called #destroy
- Update valid_to after #update
- Add GitHub Actions workflow to release to RubyGems.org
- migrate Scheduled workflows in CircleCI
- Fix JOIN query does not have valid_from / valid_to when using .or. by osyo-manga · Pull Request #99
- Fix typo in README.md by Naoya9922 · Pull Request #101
First stable release