Skip to content
This repository has been archived by the owner on Mar 3, 2020. It is now read-only.

Update mysql2: 0.5.0 → 0.5.3 (minor) #71

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Nov 28, 2019

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ mysql2 (0.5.0 → 0.5.3) · Repo · Changelog

Release Notes

0.5.3

New Features

  • Expose Windows client authentication (#1018)

Bug Fixes

  • Support more MySQL encodings and warn rather than crash on unsupported encodings (#1040)

Changes

  • Precompiled mysql2 gem for Windows supports Ruby 2.2, 2.3, 2.4, 2.5, 2.6. Windows Ruby 2.0 and 2.1 are dropped.
  • Keyword arguments have to be explicitly double-splatted in Ruby 2.7+ (#1084)
  • Add Centos to CI matrix (#989, #1085)
  • Remove spec from gem (#1044)
  • Replace Win32API with Fiddle, update appveyor.yml (#1053)
  • Update README to clarify the protocol value in DATABASE_URL (#1047)
  • Improve performance to call Mysql2::Result#each and Mysql2::Result#fields (#1046)
  • Fix fragile specs due to clock skew and timeout/threads corruption (#1041)
  • README updates (#1002, #1038)

0.5.2

New Features

None

Bug Fixes

  • Bounds-check the encoding translation array from MySQL to Ruby encodings.

Changes

  • Add more encoding translations for MySQL 8 compatibility.

0.5.1

New Features

  • None

Bug Fixes

  • Fix with --with-mysql-dir (#952)
  • Prevent command out of sync errors with Prepared Statements (#956, #957, #958)

Changes

  • Specs: Use the prepared statement performance schema if available (#960)
  • README mysql2 0.5.x works with Rails 5.0.7, 5.1.6, and higher
  • README be sure to read about the known limitations of prepared statements

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 42 commits:


Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu bot added the depfu label Nov 28, 2019
@coveralls
Copy link

Coverage Status

Coverage remained the same at 78.99% when pulling 74514f3 on depfu/update/mysql2-0.5.3 into 834bf0f on master.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant