fix(supported-version): pin-back MySQL to breaking change for tests #46
Conversation
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
damienwebdev
force-pushed
the
fixup_mysql_versions_for_tests
branch
from
4d9e305 to
c63232f
Compare
|
This error is actually in v2.4.0 surprisingly. Idk wtf to do about it. |
damienwebdev
force-pushed
the
fixup_mysql_versions_for_tests
branch
from
5859b2e to
64c57d9
Compare
damienwebdev
force-pushed
the
fixup_mysql_versions_for_tests
branch
from
64c57d9 to
b4e7831
Compare
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
On older versions of MySQL, the
PROCESSprivilege was not required. This was changed as described here: magento/magento2#30502.Fixes: graycoreio/magento2-graphql-introspection-cache#6
What is the new behavior?
We pin back to older MySQL versions on older versions of Magento.
Does this PR introduce a breaking change?
Other information