Releases: doximity/es-elasticity
v1.4.0
This updates the gem to support Rails 8.0 by bumping the relevant dependencies and replacing the deprecated [1] ActiveSupport::ProxyObject with Ruby's built-in BasicObject [2], as Rails has removed the deprecated proxy class in 8.0.
More context:
The BasicObject class has been available in Ruby since v1.9, and given that this gem has direct dependencies on activemodel/activesupport/activerecord >= 5.2.0, which themselves require a minimum Ruby version of 2.2 [3], this shouldn't introduce breaking changes for the range of Ruby versions currently supported by this gem. Additionally, the raise method that was defined by ProxyObject [4] is not being used in the gem's codebase, so this should be a clean replacement. However, we can define raise for these classes if we want to be extra conservative with the change.
[1] rails/rails#51638
[2] https://docs.ruby-lang.org/en/3.4/BasicObject.html
[3] https://rubygems.org/gems/activemodel/versions/5.2.0
[4] rails/rails/activesupport/lib/active_support/proxy_object#L13-L15
v1.2.1
v1.1.0
Updated the max Elasticsearch dependency version to < 8.7
v1.0.1
- Revert the additional
frozen_string_literalupdates in 1.0.0 due to some issues with some classes. We'll update these in a separate release to isolate the problem.
v1.0.0
- Consistently use quotations
- Update API to remove deprecation warnings for Elasticsearch 7.X.X in preparation for upgrade to 8.
- Freeze string literals
- Remove
_typefrom query/create/update/delete methods - Remove
use_new_timestamp_formatconfig - Remove
include_type_name_on_createconfig
v0.14.1
- Don't publish pre-release builds to RubyGems
v0.14.0
- Use
refreshinstead offlushwhere search is expected to be updated - Drop support for Ruby 2.5 and 2.6
- Add support for Ruby 2.7 and 3.0, build against Ruby 3.1
- Set
search_typetoquery_then_fetchas we no longer support Elasticsearch version < 7.0 - Set
include_type_namewhen fetching the mapping. Will be removed in the next version to support ES version 8. - Index names automatically use the new timestamp format when creating an index.