Uh oh!
There was an error while loading. Please reload this page.
Fix failing MinSQLAlchemy test after moving sqlalchemy spec - #38445
Merged
Conversation
Ths MIN SQLACLHEMY test was based on retrieving sqlalchemy min version from pyproject.toml but since we moved it to hatch_build.py we should read it from there.
potiuk
requested review from
Taragolis, amoghrajesh, hussein-awala, jscheffl and o-nikolasMarch 25, 2024 01:21
2 tasks
dirrao
approved these changes
Mar 25, 2024
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
3 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.
Ths MIN SQLACLHEMY test was based on retrieving sqlalchemy min version from pyproject.toml but since we moved it to hatch_build.py we should read it from there.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.