You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the gemspec, we specify the dependency on the meilisearch-ruby gem as:
s.add_dependency'meilisearch','~> 0.28'
However, the twiddle-wakka (~>) operator is not meant only for minor versions, its behavior depends on how you specify the version. ~> 0.28 will grab anything >= 0.28 and < 1, while ~> 0.28.0 will grab >= 0.28.0 to < 0.29. Source
This essentially means that our constraint does not prevent old versions of the meilisearch-rails gem from grabbing newer versions of meilisearch-ruby.
This has already caused issues with our communication failure in shipping meilisearch-ruby 0.30 with the renamed top level module, I wrongly believed that wouldn't be an issue since this rails gem would be frozen in place. See #347 (comment) .
The text was updated successfully, but these errors were encountered:
ellnix
added a commit
to ellnix/meilisearch-rails
that referenced
this issue
Jan 14, 2025
twiddle-wakka (~>) operator is not meant only for minor versions, its behavior depends on how you specify the version. ~> 0.28 will grab anything >= 0.28 and < 1, while ~> 0.28.0 will grab >= 0.28.0 to < 0.29.
For more information, see meilisearch#386 .
In the gemspec, we specify the dependency on the
meilisearch-ruby
gem as:However, the twiddle-wakka (~>) operator is not meant only for minor versions, its behavior depends on how you specify the version.
~> 0.28
will grab anything>= 0.28
and< 1
, while~> 0.28.0
will grab>= 0.28.0
to< 0.29
.Source
This essentially means that our constraint does not prevent old versions of the meilisearch-rails gem from grabbing newer versions of meilisearch-ruby.
This has already caused issues with our communication failure in shipping meilisearch-ruby 0.30 with the renamed top level module, I wrongly believed that wouldn't be an issue since this rails gem would be frozen in place. See #347 (comment) .
The text was updated successfully, but these errors were encountered: