Improve upgrade important version hook: #54606
Merged
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
potiuk
requested review from
amoghrajesh,
ashb,
gopidesupavan and
jedcunningham
as code owners
boring-cyborg
bot
added
area:dev-tools
backport-to-v3-1-test
* we do not have to check Python versions below 3.9 - that significantly speeds up the check * we run `uv sync --resolution highest` in dev/breeze when there are some changes - that will make sure that the latest version of dependencies in breeze are captured in the uv.lock file
potiuk
force-pushed
the
improve-upgrade-prek-hook
branch
from
78b3e42 to
59f8050
Compare
Member
Author
Yeah. I noticed breeze lock was out of sync after the last change and finally I found a way how we can also make it "eventually consistent". Thanks to that I have an idea how we can add uv.lock to Airflow and use the .lock instead of constraints for PRs and regular developments (we'd still generate constraints the same way we do now, but we could switch to uv.lock. Let's see how it works - but I think this |
github-actions bot
pushed a commit
that referenced
this pull request
Aug 18, 2025
* we do not have to check Python versions below 3.9 - that significantly speeds up the check * we run `uv sync --resolution highest` in dev/breeze when there are some changes - that will make sure that the latest version of dependencies in breeze are captured in the uv.lock file (cherry picked from commit c6c6d75) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
Backport successfully created: v3-0-test
|
github-actions bot
pushed a commit
to aws-mwaa/upstream-to-airflow
that referenced
this pull request
Aug 18, 2025
* we do not have to check Python versions below 3.9 - that significantly speeds up the check * we run `uv sync --resolution highest` in dev/breeze when there are some changes - that will make sure that the latest version of dependencies in breeze are captured in the uv.lock file (cherry picked from commit c6c6d75) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
potiuk
added a commit
that referenced
this pull request
Aug 18, 2025
* we do not have to check Python versions below 3.9 - that significantly speeds up the check * we run `uv sync --resolution highest` in dev/breeze when there are some changes - that will make sure that the latest version of dependencies in breeze are captured in the uv.lock file (cherry picked from commit c6c6d75) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
kaxil
pushed a commit
that referenced
this pull request
Aug 18, 2025
* we do not have to check Python versions below 3.9 - that significantly speeds up the check * we run `uv sync --resolution highest` in dev/breeze when there are some changes - that will make sure that the latest version of dependencies in breeze are captured in the uv.lock file (cherry picked from commit c6c6d75) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
Sign up for free
to 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.
we do not have to check Python versions below 3.9 - that significantly speeds up the check
we run
uv sync --resolution highestin dev/breeze when there are some changes - that will make sure that the latest version of dependencies in breeze are captured in the uv.lock file^ 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 airflow-core/newsfragments.