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

Upgrade rubyies on travis #431

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

berkos
Copy link

@berkos berkos commented Mar 16, 2019

👋

  • Upgrade to latest Rubies on Travis.
  • Remove Gemfile.lock to relax dependancies between different Ruby versions.

note: Gemfile.lock is bundled with a specific version of bundler, not sure if there is a reason to keep the lock file as versions can locked from gemspec.

Thanks!

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.0002%) to 99.368% when pulling e701247 on berkos:upgrade_rubyies_on_travis into cee52fe on floere:master.

@floere
Copy link
Owner

floere commented Mar 17, 2019

@berkos Hi Antonis!
Thanks for the PR – I like that you added the versions for Travis 👍 Much appreciated.
Regarding the Gemfile.lock – the lock is for developing the gem itself, to ensure that contributors have the same versions as I do when developing. The gemspec is for the gem's dependencies itself. They have different purposes. So if you could revert e701247, I'd be happy to pull this PR (or you could convince me, that would be fine also 😊)
Cheers and thanks again!

@berkos
Copy link
Author

berkos commented Mar 17, 2019

@berkos Hi Antonis!
Thanks for the PR – I like that you added the versions for Travis 👍 Much appreciated.
Regarding the Gemfile.lock – the lock is for developing the gem itself, to ensure that contributors have the same versions as I do when developing. The gemspec is for the gem's dependencies itself. They have different purposes. So if you could revert e701247, I'd be happy to pull this PR (or you could convince me, that would be fine also 😊)
Cheers and thanks again!

Hi @floere. Thanks very much for your reply!
Ruby 2.5.5 was failing as Bundler 1.16.6 was not available in that version.
Also of the reasons that I had the Gemfile.lock removed is because given it's a library you want to it to be available to work with a variety of clients(apps) at the moment the tests for an instance run with versions that are declared in the lock file. If someone would use the gem in his Gemfile would possible used latest version that the one used to be developed, gemspec would allow this, but the tests of the library would not have run against these versions.

I could not find an official documentation but here are some articles.
https://depfu.com/blog/2017/01/18/bundler-and-gemfile-best-practices
https://yehudakatz.com/2010/12/16/clarifying-the-roles-of-the-gemspec-and-gemfile/

I might missing something in the flow so either way I am happy to remove .lock.
Again thanks for you reply and your time 😊.

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

Successfully merging this pull request may close these issues.

3 participants