Re: [PR] Update uv version to 0.9.16 [airflow]

2025-12-06 Thread via GitHub


bugraoz93 commented on PR #59138:
URL: https://github.com/apache/airflow/pull/59138#issuecomment-3621485294

   After checking, I see that the hatch released at `2025-12-06 20:18:10 
(+01:00)` while I ran the breeze command around `Dec 6, 2025, 6:15 PM GMT+1` 
got the dates from the pages. Since you run around according to your PR 
creation datetime `Dec 6, 2025, 10:55 PM GMT+1`, when you run it, it updates 
the hatch version :slightly_smiling_face: 
   https://pypi.org/project/hatch/#history


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [PR] Update uv version to 0.9.16 [airflow]

2025-12-06 Thread via GitHub


bugraoz93 commented on PR #59138:
URL: https://github.com/apache/airflow/pull/59138#issuecomment-3621342796

   > One small thing:
   > 
   > ```
   > breeze ci upgrade
   > ```
   > 
   > This will do **all** that is needed ... Your change did not have 
everything :)  
   > 
   > https://github.com/apache/airflow/pull/59144
   > 
   > 
   > The `breeze ci upgrade` will even create a PR for you :)
   
   I used this command, I just wanted to see it this time and said no to raise 
PR. Surprised to see there was difference :)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [PR] Update uv version to 0.9.16 [airflow]

2025-12-06 Thread via GitHub


potiuk commented on PR #59138:
URL: https://github.com/apache/airflow/pull/59138#issuecomment-3621279705

   No need to backport -> https://github.com/apache/airflow/pull/59145 does the 
same in v3-1-test


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [PR] Update uv version to 0.9.16 [airflow]

2025-12-06 Thread via GitHub


potiuk commented on PR #59138:
URL: https://github.com/apache/airflow/pull/59138#issuecomment-3621276592

   One small thing:
   
   ```
   breeze ci upgrade
   ```
   
   This will do **all** that is needed ... Your change did not have everything 
:)  
   
   https://github.com/apache/airflow/pull/59144
   
   
   The `breeze ci upgrade` will even create a PR for you :)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [PR] Update uv version to 0.9.16 [airflow]

2025-12-06 Thread via GitHub


github-actions[bot] commented on PR #59138:
URL: https://github.com/apache/airflow/pull/59138#issuecomment-3621065766

   ### Backport failed to create: v3-1-test. View the failure log  Run details 

   
   
   
   Status
   Branch
   Result
   
   
   ❌
   v3-1-test
   https://github.com/apache/airflow/commit/6b4867e8169ecd8bce266efb9d4f4f3fd9b38f8d";>
   
   
   
   You can attempt to backport this manually by running:
   
   ```bash
   cherry_picker 6b4867e v3-1-test
   ```
   
   This should apply the commit to the v3-1-test branch and leave the commit in 
conflict state marking
   the files that need manual conflict resolution.
   
   After you have resolved the conflicts, you can continue the backport process 
by running:
   
   ```bash
   cherry_picker --continue
   ```
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [PR] Update uv version to 0.9.16 [airflow]

2025-12-06 Thread via GitHub


potiuk commented on PR #59138:
URL: https://github.com/apache/airflow/pull/59138#issuecomment-3621065143

   Just "rate limit" for docker 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [PR] Update uv version to 0.9.16 [airflow]

2025-12-06 Thread via GitHub


potiuk merged PR #59138:
URL: https://github.com/apache/airflow/pull/59138


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [PR] Update uv version to 0.9.16 [airflow]

2025-12-06 Thread via GitHub


bugraoz93 commented on PR #59138:
URL: https://github.com/apache/airflow/pull/59138#issuecomment-3620743404

   Why it deleted dockfile, I don't know fixing :confused: 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [PR] Update uv version to 0.9.16 [airflow]

2025-12-06 Thread via GitHub


bugraoz93 commented on PR #59138:
URL: https://github.com/apache/airflow/pull/59138#issuecomment-3620718198

   Need backport as well 
https://github.com/apache/airflow/actions/runs/19989856086


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]