We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I was looking at another gem's Travis, and there were issues with 1.9.3, and an (upgraded) rake was one of the dependencies.
Gemspec shows ruby >= 1.9.3, but it isn't tested with it. Sure its okay?
The text was updated successfully, but these errors were encountered:
It prefers to update >= 2.0.0 on gemspec.
>= 2.0.0
Sorry, something went wrong.
update required_ruby_version to 2.0.0
4135948
- as suggested by @hsbt in issue ruby#230 on github - problems with 1.9.3 have been reported, which is long EOL'd
It would be good to have an example, if not a test case for this. Still, I created a PR #236 per @hsbt's suggestion.
No branches or pull requests
I was looking at another gem's Travis, and there were issues with 1.9.3, and an (upgraded) rake was one of the dependencies.
Gemspec shows ruby >= 1.9.3, but it isn't tested with it. Sure its okay?
The text was updated successfully, but these errors were encountered: