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

Support mysql2 0.4.x and 0.5.x #32310

Merged
merged 1 commit into from
Mar 21, 2018
Merged

Support mysql2 0.4.x and 0.5.x #32310

merged 1 commit into from
Mar 21, 2018

Conversation

sodabrew
Copy link
Contributor

@sodabrew sodabrew commented Mar 21, 2018

Resolves #31636 following release of mysql2 0.5.0 today.

@rails-bot
Copy link

Thanks for the pull request, and welcome! The Rails team is excited to review your changes, and you should hear from @eileencodes (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

This repository is being automatically checked for code quality issues using Code Climate. You can see results for this analysis in the PR status below. Newly introduced issues should be fixed before a Pull Request is considered ready to review.

Please see the contribution instructions for more information.

@matthewd
Copy link
Member

You probably want to change this too:

when "mysql" then ["mysql2", ["~> 0.4.4"]]

I guess this diff tells me you at least read my comment, so that's nice 🤷‍♂️

@sodabrew
Copy link
Contributor Author

sodabrew commented Mar 21, 2018 via email

@Edouard-chin
Copy link
Member

Should this be backported to 5-2-stable? Otherwise mysql2 0.5.0 will be only usable on Rails 6.0

@kamipo
Copy link
Member

kamipo commented Mar 21, 2018

Yeah, I will do that.

@rafaelfranca
Copy link
Member

And 5-1-stable too

kamipo added a commit that referenced this pull request Mar 21, 2018
kamipo added a commit that referenced this pull request Mar 21, 2018
kamipo added a commit that referenced this pull request Mar 21, 2018
kamipo added a commit that referenced this pull request Mar 21, 2018
@kamipo
Copy link
Member

kamipo commented Mar 21, 2018

Backported in 6965f2a and 6a11d83.

@pixeltrix
Copy link
Contributor

@kamipo doesn't 6965f2a need to be in 5-2-stable? It's currently in 5-2-0 only (@rafaelfranca what's the policy here - backport to 5-2-stable and then cherry-pick what we want in 5-2-0 or backport to 5-2-0 and then that'll be merged into 5-2-stable at some point?)

@matthewd
Copy link
Member

5-2-0 will merge to 5-2-stable on release, so yeah seems fine to backport straight to there if we know it's post-rc-worthy

@kamipo
Copy link
Member

kamipo commented Mar 22, 2018

Yeah, I supposed that 5-2-0 will be merged to 5-2-stable since db7edd8 is missing in 5-2-stable yet, and I needed the commit to add CHANGELOG entry 3eadd23.

rafaelfranca pushed a commit that referenced this pull request Mar 22, 2018
@hkdnet
Copy link

hkdnet commented Mar 23, 2018

It looks that 5-0-stable also needs this patch, right?
The head of 5-0-stable does not pass the ci.
https://travis-ci.org/rails/rails/builds/357081953

@jaredbeck
Copy link
Contributor

And 5-1-stable too

Thanks for backporting ❤️

It looks that 5-0-stable also needs this patch, right?

If I understand correctly, 5.0 only receives security patches now (2018-03-23), and as soon as 5.2 is released, 5.0 will be EoL.

@pixeltrix
Copy link
Contributor

I've backported this and the dalli fix to 5-0-stable and 4-2-stable just to be on the safe side - they're still used in a lot of apps so we at least want the build to be green should the worst happen and we have to release new gems for a major security issue.

Sollace added a commit to ProjectVinyl/ProjectVinyl that referenced this pull request Mar 24, 2018
yahonda added a commit to yahonda/rails that referenced this pull request Sep 13, 2018
Rails 6 drops MySQL 5.1 support and requires MySQL 5.5.8 by rails#33853
mysql2 gem 0.5.0 also drops MySQL 5.1 support.

https://github.com/brianmario/mysql2/releases/tag/0.5.0
> MySQL 5.5 or higher required. MySQL 5.0 and 5.1 are not supported.

Related to rails#31636 rails#32310 rails#33853
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

10 participants