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

Gemfile/Gemspec Tidy (For Master) #631

Merged
merged 5 commits into from
May 31, 2019
Merged

Conversation

luke-hill
Copy link
Contributor

Summary

Tidy up Gemfile / Deps

Details

Migrate everything that could be out of gemfile conditionals into gemspec fixed values.
NB: I've also updated a few minor version restrictions. And the minimum ruby version although this was always 2.3.3 due to a dependency requirement.

Motivation and Context

Tidies things up.

How Has This Been Tested?

CI

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Refactoring (cleanup of codebase without changing any existing functionality)
  • Update documentation

Checklist:

  • I've added tests for my code
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.

@luke-hill luke-hill requested a review from mvz May 23, 2019 08:41
@luke-hill
Copy link
Contributor Author

I'll make one of these for still in a day or so.

@luke-hill
Copy link
Contributor Author

ping @mvz i've no idea if the CI here is stable or not? Could you please advise? Can this be merged?

@mvz
Copy link
Contributor

mvz commented May 30, 2019

I think an adjustment to Travis' configuration is needed. Hold on.

Our test dependencies are in the development group now. The only extra
gem that will be installed is yard-junk, but that should be fine.
spec.add_development_dependency 'pry-doc', '~> 1.0.0'
spec.add_development_dependency 'rake', '~> 12.3'
spec.add_development_dependency 'rspec', '~> 3.6'
spec.add_development_dependency 'rubocop', '~> 0.69'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be ~> 0.69.0 because the set of cops can change with each release.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with this, but I just copied the existing config, all this PR is aimed to be is a tidy up.

aruba.gemspec Outdated
spec.rubygems_version = '>= 1.6.1'
spec.required_ruby_version = '>= 2.3'
spec.required_ruby_version = '>= 2.3.3'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not a fan of excluding micro versions in general. Can we avoid this? Which of our depedencies needs 2.3.3? Maybe we need to test on 2.3.0 in Travis as well?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One of the documentation ones in the development dependencies, if we reduce it down we should be ok

@mvz
Copy link
Contributor

mvz commented May 30, 2019

The build should be green now. The signs are good 🙂.

@mvz mvz merged commit 89d6ba9 into master May 31, 2019
@mvz mvz deleted the feature/master_tidy_of_gemfile branch May 31, 2019 13:50
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.

2 participants