Closed olleolleolle closed 7 years ago
Proposal: Perhaps we could let go of 2.1?
The current JRuby 1.7 build failure is about http_form
's missing required_ruby_version
in its .gemspec which does not preclude 1.9 Rubies from automatically using it.
It'd be nice if that gem had such metadata in its .gemspec.
JRuby 1.7 is EOL'd, would it be more beneficial in the long run to hop over to JRuby 9.1.9.0?
@olleolleolle I'm sorry about that. Will fix form_data asap
@olleolleolle Can you please re-run tests. v1.0.3 of form data now fixed to play nice with jruby 1.7 and ruby 1.9+
@ixti That fixed things here! Yes!
:hearts: :yellow_heart: :green_heart: :blue_heart: :purple_heart:
@digitalextremist Is there anything more you'd like from this PR? Or, any change you'd like to see done to it?
thank you - i think this is great as a specific PR, and i'm curious as to your thoughts about my other comments and what i've done to CI and deps in my own PR. i would be happy to revert/rebase from this!
@tarcieri I'm ready for code review on this one, now.
@kenichi Oh, there we are, merged and good to go. Thank you for all of the input, it made this a lot better. Better is better!
This PR updates Ruby versions to latest releases in their series.
rake ci
inbundle exec
- update and then making it "the default Travis task" (removing its specific configuration from the Travis YAML config)rakelib
folder