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

Relax rake gem constraint from <=11.x to <=12.x. #147

Merged
merged 2 commits into from
Feb 3, 2019
Merged

Conversation

sds
Copy link
Collaborator

@sds sds commented Feb 3, 2019

Rake 12 has been released for quite some time. Given this gem doesn't depend on rake per se (it is only required to avoid installing the ffi gem on non-Windows environments), relax the constraint.

To prevent accidental breakage due to a new Rake release, we'll still pin to < 13 for now.

This also required dropping tests for Ruby 1.9, since Rake 12 (which gets installed by default now that we've relaxed the constraint) only installs on Ruby 2.x or newer. This is fine, as Ruby 1.9 reached EOL on February 23, 2015.

Rake 12 has been released for quite some time. Given this gem doesn't
depend on `rake` per se (it is only required to avoid installing the
`ffi` gem on non-Windows environments), relax the constraint.

To prevent accidental breakage due to a new Rake release, we'll still
pin to < 13 for now.
Tests against Ruby 1.9 fail because installing a recent version of Rake
(12.x) requires Ruby 2.x or newer.

Ruby 1.9 reached EOL on February 23, 2015:
https://www.ruby-lang.org/en/news/2015/02/23/support-for-ruby-1-9-3-has-ended/

For this reason, we're going to stop testing against it.
@sds
Copy link
Collaborator Author

sds commented Feb 3, 2019

The AppVeyor build failure for the branch appears spurious, since the build for the PR succeeded.

Travis build passed. Going to merge.

@sds sds merged commit 6b25d2d into dev Feb 3, 2019
@sds sds deleted the relax-rake-constraint branch February 3, 2019 06:49
@coveralls
Copy link

Coverage Status

Coverage decreased (-3.9%) to 90.819% when pulling af1b17f on relax-rake-constraint into 37e6c0a on dev.

13 similar comments
@coveralls
Copy link

Coverage Status

Coverage decreased (-3.9%) to 90.819% when pulling af1b17f on relax-rake-constraint into 37e6c0a on dev.

@coveralls
Copy link

Coverage Status

Coverage decreased (-3.9%) to 90.819% when pulling af1b17f on relax-rake-constraint into 37e6c0a on dev.

@coveralls
Copy link

Coverage Status

Coverage decreased (-3.9%) to 90.819% when pulling af1b17f on relax-rake-constraint into 37e6c0a on dev.

@coveralls
Copy link

Coverage Status

Coverage decreased (-3.9%) to 90.819% when pulling af1b17f on relax-rake-constraint into 37e6c0a on dev.

@coveralls
Copy link

Coverage Status

Coverage decreased (-3.9%) to 90.819% when pulling af1b17f on relax-rake-constraint into 37e6c0a on dev.

@coveralls
Copy link

Coverage Status

Coverage decreased (-3.9%) to 90.819% when pulling af1b17f on relax-rake-constraint into 37e6c0a on dev.

@coveralls
Copy link

Coverage Status

Coverage decreased (-3.9%) to 90.819% when pulling af1b17f on relax-rake-constraint into 37e6c0a on dev.

@coveralls
Copy link

Coverage Status

Coverage decreased (-3.9%) to 90.819% when pulling af1b17f on relax-rake-constraint into 37e6c0a on dev.

@coveralls
Copy link

Coverage Status

Coverage decreased (-3.9%) to 90.819% when pulling af1b17f on relax-rake-constraint into 37e6c0a on dev.

@coveralls
Copy link

Coverage Status

Coverage decreased (-3.9%) to 90.819% when pulling af1b17f on relax-rake-constraint into 37e6c0a on dev.

@coveralls
Copy link

Coverage Status

Coverage decreased (-3.9%) to 90.819% when pulling af1b17f on relax-rake-constraint into 37e6c0a on dev.

@coveralls
Copy link

Coverage Status

Coverage decreased (-3.9%) to 90.819% when pulling af1b17f on relax-rake-constraint into 37e6c0a on dev.

@coveralls
Copy link

Coverage Status

Coverage decreased (-3.9%) to 90.819% when pulling af1b17f on relax-rake-constraint into 37e6c0a on dev.

netbsd-srcmastr pushed a commit to NetBSD/pkgsrc that referenced this pull request Mar 24, 2020
Update ruby-childprocessto 3.0.0.


### Version 3.0.0 / 2019-09-20

* [#156](enkessler/childprocess#156 unused `rubyforge_project` from gemspec
* [#160](enkessler/childprocess#160): Remove extension to conditionally install `ffi` gem on Windows platforms
* [#160](enkessler/childprocess#160): Remove runtime dependency on `rake` gem

### Version 2.0.0 / 2019-07-11

* [#148](enkessler/childprocess#148): Drop support for Ruby 2.0, 2.1, and 2.2
* [#149](enkessler/childprocess#149): Fix Unix fork reopen to be compatible with Ruby 2.6
* [#152](https://github.com/enkessler/childprocess/pull/152)/[#154](https://github.com/enkessler/childprocess/pull/154): Fix hangs and permission errors introduced in Ruby 2.6 for leader processes of process groups

### Version 1.0.1 / 2019-02-03

* [#143](enkessler/childprocess#144): Fix installs by adding `rake` gem as runtime dependency
* [#147](enkessler/childprocess#147): Relax `rake` gem constraint from `< 12` to `< 13`

### Version 1.0.0 / 2019-01-28

* [#134](enkessler/childprocess#134): Add support for non-ASCII characters on Windows
* [#132](enkessler/childprocess#132): Install `ffi` gem requirement on Windows only
* [#128](enkessler/childprocess#128): Convert environment variable values to strings when `posix_spawn` enabled
* [#141](enkessler/childprocess#141): Support JRuby on Java >= 9
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