Upgrade prek, prek hooks, breeze lock and other important deps #54726
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
After j178/prek#35 has been completed and released in `prek` 0.1.1 we can bring back the functionality of flagging when our prek hooks need to be updated. This PR brings minimum version of prek to 0.1.1 as well as upgrades all other important versions up, upgrades breeze uv.lock and brings back the steps in upgrade check to check for auto-upgradeable hooks.
potiuk
requested review from
amoghrajesh,
ashb,
gopidesupavan and
jedcunningham
as code owners
boring-cyborg
bot
added
area:dev-tools
area:production-image
kaxil
approved these changes
Aug 20, 2025
Backport failed to create: v3-0-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker f187852 v3-0-testThis should apply the commit to the v3-0-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continue |
potiuk
added a commit
to potiuk/airflow
that referenced
this pull request
Aug 20, 2025
… deps (apache#54726) After j178/prek#35 has been completed and released in `prek` 0.1.1 we can bring back the functionality of flagging when our prek hooks need to be updated. This PR brings minimum version of prek to 0.1.1 as well as upgrades all other important versions up, upgrades breeze uv.lock and brings back the steps in upgrade check to check for auto-upgradeable hooks. (cherry picked from commit f187852) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
potiuk
added a commit
to potiuk/airflow
that referenced
this pull request
Aug 20, 2025
… deps (apache#54726) After j178/prek#35 has been completed and released in `prek` 0.1.1 we can bring back the functionality of flagging when our prek hooks need to be updated. This PR brings minimum version of prek to 0.1.1 as well as upgrades all other important versions up, upgrades breeze uv.lock and brings back the steps in upgrade check to check for auto-upgradeable hooks. (cherry picked from commit f187852) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
potiuk
added a commit
that referenced
this pull request
Aug 20, 2025
… deps (#54726) (#54734) After j178/prek#35 has been completed and released in `prek` 0.1.1 we can bring back the functionality of flagging when our prek hooks need to be updated. This PR brings minimum version of prek to 0.1.1 as well as upgrades all other important versions up, upgrades breeze uv.lock and brings back the steps in upgrade check to check for auto-upgradeable hooks. (cherry picked from commit f187852)
mangal-vairalkar
pushed a commit
to mangal-vairalkar/airflow
that referenced
this pull request
Aug 30, 2025
…e#54726) After j178/prek#35 has been completed and released in `prek` 0.1.1 we can bring back the functionality of flagging when our prek hooks need to be updated. This PR brings minimum version of prek to 0.1.1 as well as upgrades all other important versions up, upgrades breeze uv.lock and brings back the steps in upgrade check to check for auto-upgradeable hooks.
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.
After j178/prek#35 has been completed and released in
prek0.1.1 we can bring back the functionality of flagging when our prek hooks need to be updated.This PR brings minimum version of prek to 0.1.1 as well as upgrades all other important versions up, upgrades breeze uv.lock and brings back the steps in upgrade check to check for auto-upgradeable hooks.
^ 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.