Update Gem dependencies about meilisearch-rails HOT 6 OPEN

Hi @jeremylynch I just stumble upon your issue.

We are using the ~> 0.26.0 so it should already allow you to update your meilisearch-ruby and meilisearch-rails version, no?

from meilisearch-rails.

We are using the ~> 0.26.0 so it should already allow you to update your meilisearch-ruby and meilisearch-rails version, no?

~> only allows an update to the patch version, not the minor version.

From the bundler documentation:

gem "rails", "~> 4.0.0" # which is same as gem "rails", ">= 4.0.0", "< 4.1.0" 

from meilisearch-rails.

Oh yeah, my bad! https://thoughtbot.com/blog/rubys-pessimistic-operator

@ellnix I'm ok if you raise the dependency to >= 0.26.0

from meilisearch-rails.

@ellnix I'm ok if you raise the dependency to >= 0.26.0

I think we should stick with ~> and updating the version manually. If I change the requirement to >=, someone might want to use ms-rails 0.14 as we intended it and end up with a much later of ms-ruby that may no longer be compatible.

In any case, should I PR this and also make a 0.13.1 release? (I feel like it would be better to update that on a minor version)

from meilisearch-rails.

In any case, should I PR this and also make a 0.13.1 release? (I feel like it would be better to update that on a minor version)

In my mind, we could always ignore the versions that are not compatible using != version or just increase the starting point, let's say meilisearch-ruby >= 0.30.0. And we always ask the users to be on the latest on both sides :D

But as you wish! I was trying to reduce the amount of work 😅

from meilisearch-rails.

Any update on this one?

from meilisearch-rails.