Upgrade to prek 0.0.29 #54621
Merged
Upgrade to prek 0.0.29 #54621
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
This upgrades prek to **just released** 0.0.29 and removes the workaround implemented in apache#54613 to add build-essential to the image that is used to build distributions - because prek 0.0.29 comes with all the necessary binary wheels/platforms that remove the need to build in in our Linux ARM image (issue j178/prek#451 has been fixed).
potiuk
requested review from
amoghrajesh,
ashb,
gopidesupavan and
jedcunningham
as code owners
boring-cyborg
bot
added
area:dev-tools
backport-to-v3-1-test
eladkal
approved these changes
Aug 18, 2025
gopidesupavan
approved these changes
Aug 18, 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 a4fa218 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 18, 2025
This upgrades prek to **just released** 0.0.29 and removes the workaround implemented in apache#54613 to add build-essential to the image that is used to build distributions - because prek 0.0.29 comes with all the necessary binary wheels/platforms that remove the need to build in in our Linux ARM image (issue j178/prek#451 has been fixed). (cherry picked from commit a4fa218) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
potiuk
added a commit
that referenced
this pull request
Aug 18, 2025
This upgrades prek to **just released** 0.0.29 and removes the workaround implemented in #54613 to add build-essential to the image that is used to build distributions - because prek 0.0.29 comes with all the necessary binary wheels/platforms that remove the need to build in in our Linux ARM image (issue j178/prek#451 has been fixed). (cherry picked from commit a4fa218)
mangal-vairalkar
pushed a commit
to mangal-vairalkar/airflow
that referenced
this pull request
Aug 30, 2025
This upgrades prek to **just released** 0.0.29 and removes the workaround implemented in apache#54613 to add build-essential to the image that is used to build distributions - because prek 0.0.29 comes with all the necessary binary wheels/platforms that remove the need to build in in our Linux ARM image (issue j178/prek#451 has been fixed).
Sign up for free
to 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.
This upgrades prek to just released 0.0.29 and removes the workaround implemented in #54613 to add build-essential to the image that is used to build distributions - because prek 0.0.29 comes with all the necessary binary wheels/platforms that remove the need to build in in our Linux ARM image (issue j178/prek#451 has been fixed).
^ 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.