Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compatibility with i18n v1.1 #278

Closed
omitter opened this issue Sep 20, 2018 · 4 comments
Closed

Compatibility with i18n v1.1 #278

omitter opened this issue Sep 20, 2018 · 4 comments

Comments

@omitter
Copy link
Contributor

omitter commented Sep 20, 2018

Adding Mobility to my projects Gemfile forced a downgrade on the gem i18n from v1.1.0 to v1.0.1. Is this really necessary? Maybe the gemspec is just too strict?

Bundler could not find compatible versions for gem "i18n":
  In snapshot (Gemfile.lock):                                                                                                                                
    i18n (= 1.1.0)                                                                                                                                           

  In Gemfile:                                                                                                                                                
    mobility (~> 0.8.0) was resolved to 0.8.0, which depends on                                                                                              
      i18n (< 1.1, >= 0.6.10)

If i18n uses semantic versioning, i18n (< 2, >= 0.6.10) should work in the gemspec. In case it's really not working, I hope you support i18n 1.1 from the next version on.

@shioyama
Copy link
Owner

Thanks for pointing this out. Yes probably the gemspec is too strict. Could you make a PR with that change to the gemspec? I'm planning to release some minor changes in 0.8.1 so I can include this change in there as well.

@shioyama
Copy link
Owner

Should be no issue if the specs pass on the PR.

@shioyama
Copy link
Owner

Created a PR for this, will merge+release if/once specs pass.

@shioyama
Copy link
Owner

The fix for this was released in 0.8.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants