chore: fix MySQL client to disable SSL verification#443
Closed
tyloo wants to merge 1 commit into
Closed
Conversation
tleon
previously approved these changes
Sep 2, 2025
Quetzacoalt91
dismissed
tleon’s stale review
September 2, 2025 08:25
Dismissing review as the changes needed to be tested first. More changes need to be added.
tyloo
force-pushed
the
chore/fix-mysql-client-version
branch
from
September 2, 2025 09:09
c966cec to
928ab52
Compare
tyloo
changed the title
tyloo
force-pushed
the
chore/fix-mysql-client-version
branch
from
September 2, 2025 09:10
928ab52 to
ff8b94a
Compare
Signed-off-by: Julien Bonvarlet <julien.bonvarlet@prestashop.com>
tyloo
force-pushed
the
chore/fix-mysql-client-version
branch
from
September 2, 2025 09:22
ff8b94a to
301c1dc
Compare
nicosomb
approved these changes
Sep 2, 2025
Author
|
Close in favor of #444 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
My assumption is that the default-mysql-client package has been updated from 1.0.7 to 1.1.1.
This PR forces the
ssl=0option to fix those blocking issues.