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

specify ruby 2.0 or better as required in the gemspec #57

Merged
merged 1 commit into from
Aug 12, 2024

Conversation

yob
Copy link
Contributor

@yob yob commented Sep 19, 2017

The README says only version 2.0 or better is supported, and the travis config runs builds on 2.0 and up.

By aligning the gemspec with both those locations, installers of the gem will be clearly notified when they're running an unsupported ruby version.

The README says only version 2.0 or better is supported, and the travis
config runs builds on 2.0 and up.

By aligning the gemspec with both those locations, installers of the gem
will be clearly notified when they're running an unsupported ruby
version.
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 2a3fc81 on yob:ruby-version into 7f384d5 on campaignmonitor:master.

2 similar comments
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 2a3fc81 on yob:ruby-version into 7f384d5 on campaignmonitor:master.

@coveralls
Copy link

coveralls commented Sep 19, 2017

Coverage Status

Coverage remained the same at 100.0% when pulling 2a3fc81 on yob:ruby-version into 7f384d5 on campaignmonitor:master.

@henrys-cm henrys-cm merged commit 240b8db into campaignmonitor:master Aug 12, 2024
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