Uh oh!
There was an error while loading. Please reload this page.
[v3-2-test] Cap pymysql<1.2 in PyPI constraints generation (#67491) - #67492
Merged
Conversation
The released apache-airflow-providers-mysql on PyPI does not yet carry the pymysql<1.2 cap from #67467, so PyPI constraint generation picks up pymysql 1.2.0 and breaks SQLAlchemy's AsyncAdapt_aiomysql_connection.ping(). Mirror the cap in the constraints script's additional_constraints_for_highest_resolution so PyPI constraints stay installable until the SQLAlchemy fix is released. Also extend the comment in providers/mysql/pyproject.toml to link the upstream tracking issue (sqlalchemy/sqlalchemy#13306). (cherry picked from commit 6e9757b) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
1 task
potiuk
marked this pull request as ready for review
May 25, 2026 20:08
potiuk
requested review from
amoghrajesh, ashb, bugraoz93, gopidesupavan, jason810496, jscheffl and potiuk
as code ownersMay 25, 2026 20:08
Uh oh!
There was an error while loading. Please reload this page.
vatsrahul1001 pushed a commit
that referenced
this pull request
May 25, 2026
…67492) The released apache-airflow-providers-mysql on PyPI does not yet carry the pymysql<1.2 cap from #67467, so PyPI constraint generation picks up pymysql 1.2.0 and breaks SQLAlchemy's AsyncAdapt_aiomysql_connection.ping(). Mirror the cap in the constraints script's additional_constraints_for_highest_resolution so PyPI constraints stay installable until the SQLAlchemy fix is released. Also extend the comment in providers/mysql/pyproject.toml to link the upstream tracking issue (sqlalchemy/sqlalchemy#13306). (cherry picked from commit 6e9757b) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
vatsrahul1001 pushed a commit
that referenced
this pull request
May 25, 2026
…67492) The released apache-airflow-providers-mysql on PyPI does not yet carry the pymysql<1.2 cap from #67467, so PyPI constraint generation picks up pymysql 1.2.0 and breaks SQLAlchemy's AsyncAdapt_aiomysql_connection.ping(). Mirror the cap in the constraints script's additional_constraints_for_highest_resolution so PyPI constraints stay installable until the SQLAlchemy fix is released. Also extend the comment in providers/mysql/pyproject.toml to link the upstream tracking issue (sqlalchemy/sqlalchemy#13306). (cherry picked from commit 6e9757b) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
The released apache-airflow-providers-mysql on PyPI does not yet carry
the pymysql<1.2 cap from #67467, so PyPI constraint generation picks up
pymysql 1.2.0 and breaks SQLAlchemy's AsyncAdapt_aiomysql_connection.ping().
Mirror the cap in the constraints script's additional_constraints_for_highest_resolution
so PyPI constraints stay installable until the SQLAlchemy fix is released.
Also extend the comment in providers/mysql/pyproject.toml to link the
upstream tracking issue (sqlalchemy/sqlalchemy#13306).
(cherry picked from commit 6e9757b)
Co-authored-by: Jarek Potiuk jarek@potiuk.com