Slightly speed up package preparation and upgrade latest build deps #52909
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
area:production-image
jscheffl
approved these changes
Jul 5, 2025
potiuk
force-pushed
the
add-pre-commit-uv-to-package-building
branch
from
80e3c61 to
12b277c
Compare
potiuk
changed the title
potiuk
force-pushed
the
add-pre-commit-uv-to-package-building
branch
2 times, most recently
from
6bc387e to
fd8efe1
Compare
potiuk
changed the title
Member
Author
|
Added also gitpython and rich - noticed those were not updated either. |
I noticed that we did not have `pre-commit-uv` in the image that was building the distribution packages. Adding it should slightly speed up building such an image for isolated package preparation. The `uv` has been upgraded along the way, also the comment that we should automate updating the versions in release_management_command.py has been removed - because we already have automation in place. The missing pieces were adding "hatch", "pyyaml", "gitpython" and "rich".
potiuk
force-pushed
the
add-pre-commit-uv-to-package-building
branch
from
fd8efe1 to
635b77e
Compare
eladkal
approved these changes
Jul 5, 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 bbc8f74 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
Jul 5, 2025
…build deps (apache#52909) I noticed that we did not have `pre-commit-uv` in the image that was building the distribution packages. Adding it should slightly speed up building such an image for isolated package preparation. The `uv` has been upgraded along the way, also the comment that we should automate updating the versions in release_management_command.py has been removed - because we already have automation in place. The missing pieces were adding "hatch", "pyyaml", "gitpython" and "rich". (cherry picked from commit bbc8f74) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
potiuk
added a commit
that referenced
this pull request
Jul 5, 2025
…build deps (#52909) (#52924) I noticed that we did not have `pre-commit-uv` in the image that was building the distribution packages. Adding it should slightly speed up building such an image for isolated package preparation. The `uv` has been upgraded along the way, also the comment that we should automate updating the versions in release_management_command.py has been removed - because we already have automation in place. The missing pieces were adding "hatch", "pyyaml", "gitpython" and "rich". (cherry picked from commit bbc8f74)
kaxil
pushed a commit
that referenced
this pull request
Jul 7, 2025
…build deps (#52909) (#52924) I noticed that we did not have `pre-commit-uv` in the image that was building the distribution packages. Adding it should slightly speed up building such an image for isolated package preparation. The `uv` has been upgraded along the way, also the comment that we should automate updating the versions in release_management_command.py has been removed - because we already have automation in place. The missing pieces were adding "hatch", "pyyaml", "gitpython" and "rich". (cherry picked from commit bbc8f74)
HsiuChuanHsu
pushed a commit
to HsiuChuanHsu/airflow
that referenced
this pull request
Jul 10, 2025
…pache#52909) I noticed that we did not have `pre-commit-uv` in the image that was building the distribution packages. Adding it should slightly speed up building such an image for isolated package preparation. The `uv` has been upgraded along the way, also the comment that we should automate updating the versions in release_management_command.py has been removed - because we already have automation in place. The missing pieces were adding "hatch", "pyyaml", "gitpython" and "rich".
stephen-bracken
pushed a commit
to stephen-bracken/airflow
that referenced
this pull request
Jul 15, 2025
…pache#52909) I noticed that we did not have `pre-commit-uv` in the image that was building the distribution packages. Adding it should slightly speed up building such an image for isolated package preparation. The `uv` has been upgraded along the way, also the comment that we should automate updating the versions in release_management_command.py has been removed - because we already have automation in place. The missing pieces were adding "hatch", "pyyaml", "gitpython" and "rich".
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.
I noticed that we did not have
pre-commit-uvin the image that was building the distribution packages. Adding it should slightly speed up building such an image for isolated package preparation.The
uvhas been upgraded along the way, also the comment that we should automate updating the versions inrelease_management_command.py has been removed - because we already have automation in place. The missing pieces were adding "hatch", "pyyaml", "gitpython" and "rich".
^ 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.