v0.11.2

What's Changed

• test: use DatabaseCleaner for Rails < 6 by @olleolleolle in #133
• Document differences between this gem and ActiveRecord::Persistence#upsert by @its-fern in #131
• fix: update rails default branch name by @olleolleolle in #134
• Test with Ruby 3.1 on Rails => 7.0.1 by @jesjos in #136
• README: add section on Alternatives [ci skip] by @olleolleolle in #137
• Add support for Ruby 3.2 and Rails 7.1 by @jgraichen in #139
• Update build badge in README.md by @olleolleolle in #141
• Add v0.11.2, fix readme formatting by @olleolleolle in #142

New Contributors

• @its-fern made their first contribution in #131
• @jgraichen made their first contribution in #139

Full Changelog: v0.11.1...v0.11.2

v0.11.1

• Add Rails 7 compatibility
• Drop support for Rails 5.0 and Rails 5.1
• Add official support for Ruby 3.0

(v0.11.0 was a misrelease, it lacked the version bump.)

v0.10.1

• Nick Campbell fixed #113 so that upserting a record clears the "dirty state"

v0.10.0

• #93 Add upsert_keys and upsert_options as opts
• #94 Improve quality of logs
• #99 Document gotcha with database default values
• #105 Fix query cache reset in Rails 6
• #108 Add Rails 6.1 support

Thanks @jherdman for supporting this release!

v0.9.5

• #92 Support Rails 6

All commits since last version.

v0.9.4

This release fixes regressions that were present at least in 0.9.2 and 0.9.3, which caused this gem to be incompatible with Rails < 5.2.

Due to an error in our build matrix, we weren't properly testing against other versions of Rails.

Bugfixes

Broken backwards compatibility. (#79)
Broken build matrix. (#81 )

Other

Build against proper Rails 5.2 release. (#80 )

v0.9.3

NB: B/c of a broken build matrix, v0.9.2 and v0.9.3 are incompatible with rails < 5.2.1!

Bugfixes

• #78 Avoid a conversion which could raise errors on very large transaction IDs

v0.9.2

NB: B/c of a broken build matrix, v0.9.2 and v0.9.3 are incompatible with rails < 5.2.1!

Bugfixes

• #77 Fixes related to updated attributes (Issue #72)
• #75 Add upsert_operation to know whether an operation was insert or update

v0.9.1

Actual release of v0.9.0.

• #70 Feature: Allow upserting on a custom field
• #71 Repair specs about upsert_keys and literals

v0.9.0

• #70 Feature: Allow upserting on a custom field
• #71 Repair specs about upsert_keys and literals