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

Remove explicit support for Rubies 1.8 and 1.9 #185

Merged
merged 1 commit into from Nov 15, 2018

Conversation

tjschuck
Copy link
Collaborator

As I've repeatedly threatened, I would keep supporting 1.8 and 1.9 until it became too difficult to do so.

Well, that time has come. I've sunk too many hours into these at this point, and the 4.0 release we're heading towards is a good time to drop explicit support.

They're still implicitly supported in the sense that there's not necessarily anything stopping a user from figuring out how to get them up and running (all of the difficulty is environmental, not bcrypt-ruby's code — compilers and OpenSSLs and CI and installing the Rubies themselves), but I'm not going to let 1.8 and 1.9 test failures be blocking anymore.

@tjschuck
Copy link
Collaborator Author

The Windows tests are still failing due to #184, but these two have a circular dependency on each other to get to fully green CI 😅

I'm just going to merge this, CI be damned, and then use #184's green CI as my mandate.

@tjschuck tjschuck merged commit 66d4979 into master Nov 15, 2018
@tjschuck tjschuck deleted the drop_rubies_1-8_and_1-9 branch November 15, 2018 17:43
tjschuck added a commit that referenced this pull request Nov 15, 2018
REE is a 1.8-compatible Ruby, so drop it along with the rest of the 1.8s and 1.9s in #185
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.

None yet

1 participant