CI: Upgrade important CI environment

[jscheffl]

See https://github.com/apache/airflow/actions/runs/21879965340

---

Was generative AI tooling used to co-author this PR?

• No (please specify the tool below)

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[potiuk]

I wonder why so many "SVG" changes - looks like for some reason all images in Breeze have been regenerated - they have a differnt hash ...

Not sure why ?

[potiuk]

I just run it manually - #61748 - and there are no such changes ...

[jscheffl]

Was wndering myself-.. if you is getting green also OK to merge this...

[jscheffl]

breeze ci upgrademade it's job and failed in commit... because the automed prek on my side re-generated the outputs... then just added them... was wondering myself. Was my CI image outdated? Thought the SVG's are generated Docker-free...

[potiuk]

breeze ci upgrademade it's job and failed in commit... because the automed prek on my side re-generated the outputs... then just added them... was wondering myself. Was my CI image outdated? Thought the SVG's are generated Docker-free...

Hmm. strange indeed.. They should be outside.. Maybe it's a python version thing (the python version used to install breeze) ?

uv tool list -vv 

DEBUG Checking for Python environment at: `/Users/jarekpotiuk/.local/share/uv/tools/apache-airflow-breeze`
TR`ACE Found cached interpreter info for Python 3.13.7, skipping query of: /Users/jarekpotiuk/.local/share/uv/tools/apache-airflow-breeze/bin/python3
DEBUG Found existing environment for tool `apache-airflow-breeze`: /Users/jarekpotiuk/.local/share/uv/tools/apache-airflow-breeze
apache-airflow-breeze v0.0.1
- breeze

[jscheffl]

breeze ci upgrademade it's job and failed in commit... because the automed prek on my side re-generated the outputs... then just added them... was wondering myself. Was my CI image outdated? Thought the SVG's are generated Docker-free...

Hmm. strange indeed.. They should be outside.. Maybe it's a python version thing (the python version used to install breeze) ?

Not sure...

(apache-airflow) jscheffl@hp860g9:~/Workspace/airflow$ uv tool list -vv 
DEBUG uv 0.10.0
TRACE Checking lock for `/home/jscheffl/.cache/uv` at `/home/jscheffl/.cache/uv/.lock`
DEBUG Acquired shared lock for `/home/jscheffl/.cache/uv`
TRACE Checking lock for `/home/jscheffl/.local/share/uv/tools` at `/home/jscheffl/.local/share/uv/tools/.lock`
DEBUG Acquired exclusive lock for `/home/jscheffl/.local/share/uv/tools`
DEBUG Checking for Python environment at: `/home/jscheffl/.local/share/uv/tools/apache-airflow-breeze`
TRACE Found cached interpreter info for Python 3.10.17, skipping query of: /home/jscheffl/.local/share/uv/tools/apache-airflow-breeze/bin/python3
DEBUG Found existing environment for tool `apache-airflow-breeze`: /home/jscheffl/.local/share/uv/tools/apache-airflow-breeze
apache-airflow-breeze v0.0.1
- breeze
DEBUG Checking for Python environment at: `/home/jscheffl/.local/share/uv/tools/cherry-picker`
TRACE Querying interpreter executable at /home/jscheffl/.local/share/uv/tools/cherry-picker/bin/python3
DEBUG Found existing environment for tool `cherry-picker`: /home/jscheffl/.local/share/uv/tools/cherry-picker
cherry-picker v2.6.0
- cherry_picker
DEBUG Checking for Python environment at: `/home/jscheffl/.local/share/uv/tools/diffoscope`
TRACE Querying interpreter executable at /home/jscheffl/.local/share/uv/tools/diffoscope/bin/python3
DEBUG Found existing environment for tool `diffoscope`: /home/jscheffl/.local/share/uv/tools/diffoscope
diffoscope v306
- diffoscope
DEBUG Checking for Python environment at: `/home/jscheffl/.local/share/uv/tools/twine`
TRACE Querying interpreter executable at /home/jscheffl/.local/share/uv/tools/twine/bin/python3
DEBUG Found existing environment for tool `twine`: /home/jscheffl/.local/share/uv/tools/twine
twine v6.2.0
- twine
DEBUG Checking for Python environment at: `/home/jscheffl/.local/share/uv/tools/ty`
TRACE Querying interpreter executable at /home/jscheffl/.local/share/uv/tools/ty/bin/python3
DEBUG Found existing environment for tool `ty`: /home/jscheffl/.local/share/uv/tools/ty
ty v0.0.6
- ty
DEBUG Released lock at `/home/jscheffl/.local/share/uv/tools/.lock`
DEBUG Released lock at `/home/jscheffl/.cache/uv/.lock`

[bugraoz93]

I merged min prek version PR and maybe uv upgraded that for you and somehow impacted this. Could it be relate? 🤔

[jscheffl]

Okay, killed my venv, upgraded all UV tools and then it was not re-generating the SVG's. Let's merge Jareks PR!