Re: [PR] [main] Upgrade important CI environment [airflow]

2026-07-16 Thread via GitHub


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

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

   
   Note: As of [Merging PRs targeted for Airflow 
3.X](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#merging-prs-targeted-for-airflow-3x)
   the committer who merges the PR is responsible for backporting the PRs that 
are bug fixes (generally speaking) to the maintenance branches.
   
   In matter of doubt please ask in 
[#release-management](https://apache-airflow.slack.com/archives/C03G9H97MM2) 
Slack channel.
   
   
   
   Status
   Branch
   Result
   
   
   ❌
   v3-3-test
   https://github.com/apache/airflow/commit/c8d313a5d250018f87d4c43695298a27713dac20";>
   
   
   
   You can attempt to backport this manually by running:
   
   ```bash
   cherry_picker c8d313a v3-3-test
   ```
   
   This should apply the commit to the v3-3-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
   ```
   
   If you don't have cherry-picker installed, see the [installation 
guide](https://github.com/apache/airflow/blob/main/dev/README.md#how-to-backport-pr-with-cherry-picker-cli).
   


-- 
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] [main] Upgrade important CI environment [airflow]

2026-07-16 Thread via GitHub


Lee-W merged PR #69694:
URL: https://github.com/apache/airflow/pull/69694


-- 
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] [main] Upgrade important CI environment [airflow]

2026-07-15 Thread via GitHub


Lee-W commented on PR #69694:
URL: https://github.com/apache/airflow/pull/69694#issuecomment-4988940821

   Merged and rebased. Let's see how it works this time


-- 
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] [main] Upgrade important CI environment [airflow]

2026-07-15 Thread via GitHub


FrankYang0529 commented on PR #69694:
URL: https://github.com/apache/airflow/pull/69694#issuecomment-4988389925

   Fix mypy 2.2.0 check.
   
   https://github.com/apache/airflow/pull/69946
   https://github.com/apache/airflow/actions/runs/29464276931/job/87516317103
   
   ```
   
providers/apache/beam/src/airflow/providers/apache/beam/hooks/beam.py:184: 
error: Value of type variable "_R" of "select" cannot be "IO[Any] | None"  
[type-var]
   readable_fds, _, _ = select.select(reads, [], [], 5)
^~~
   Found 1 error in 1 file (checked 4688 source files)
   ```


-- 
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] [main] Upgrade important CI environment [airflow]

2026-07-15 Thread via GitHub


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

   
   `uv.lock` on `main` just moved via 
[#69924](https://github.com/apache/airflow/pull/69924) ("Support excluding 
files from `common.ai` Agent Skills discovery"), commit 
[`663a792`](https://github.com/apache/airflow/commit/663a79203891e04111e4a0cea079cc34011a9ad9)
 and this PR currently conflicts.
   
   Quickest fix:
   ```bash
   git fetch upstream main && git rebase upstream/main
   rm uv.lock && uv lock
   git add uv.lock && git rebase --continue
   git push --force-with-lease
   ```
   
   _Automated nudge — ignore if you're not ready to rebase. This comment is 
updated in place on future `uv.lock` bumps._


-- 
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] [main] Upgrade important CI environment [airflow]

2026-07-12 Thread via GitHub


FrankYang0529 commented on PR #69694:
URL: https://github.com/apache/airflow/pull/69694#issuecomment-4954926181

   Previously, the failed case was:
   
   ```
   
providers/common/ai/tests/unit/common/ai/operators/test_llamaindex_embedding.py::TestEmbeddingOperatorPersist::test_persist_path_embeds_each_chunk_once_with_real_llama_index
 - AttributeError: 'RefDocInfo' object has no attribute 'to_dict'
   ```
   
   After generating new `uv.lock`, previous failed case has gone. There are two 
new error cases:
   
   1. `azure-mgmt-datafactory` 9.3.0 → 10.0.0
   
   ```
   
providers/microsoft/azure/src/airflow/providers/microsoft/azure/hooks/data_factory.py:925:
 error: No overload variant of "create_or_update" of "TriggersOperations" 
matches argument types "str", "str",
   "str", "TriggerResource", "str | None", "dict[str, Any]"  [call-overload]
   return self.get_conn().triggers.create_or_update(
   ```
   
   2. `rich` 13.9.4 → 14.3.4
   
   ```
   TestCheatSheetCommand.test_should_display_index 
_
   [gw1] linux -- Python 3.10.20 /usr/local/bin/python3
   airflow-core/tests/unit/cli/commands/test_cheat_sheet_command.py:100: in 
test_should_display_index
   assert ALL_COMMANDS in output
   E   AssertionError: assert 'airflow cmd_b   
| Help text D\n' in 'Miscellaneous commands 
 \nairflow cmd_b  | Help t...w cmd_e cmd_g  
  | Help text G\n   
 \n'
   ```
   
   I will create two PRs to fix each case.


-- 
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] [main] Upgrade important CI environment [airflow]

2026-07-12 Thread via GitHub


Lee-W commented on code in PR #69694:
URL: https://github.com/apache/airflow/pull/69694#discussion_r3566496452


##
uv.lock:
##
@@ -11289,15 +11323,16 @@ wheels = [
 
 [[package]]
 name = "dataclasses-json"
-version = "0.6.7"
+version = "0.2.5"

Review Comment:
   pushed. let's see how it works now



-- 
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] [main] Upgrade important CI environment [airflow]

2026-07-12 Thread via GitHub


FrankYang0529 commented on code in PR #69694:
URL: https://github.com/apache/airflow/pull/69694#discussion_r3566267819


##
uv.lock:
##
@@ -11289,15 +11323,16 @@ wheels = [
 
 [[package]]
 name = "dataclasses-json"
-version = "0.6.7"
+version = "0.2.5"

Review Comment:
   We may need to rerun the workflow to generate a new `uv.lock`. The 
`dataclasses-json` here is still `0.2.5`.



-- 
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] [main] Upgrade important CI environment [airflow]

2026-07-12 Thread via GitHub


Lee-W commented on PR #69694:
URL: https://github.com/apache/airflow/pull/69694#issuecomment-4950441333

   I forget I was waiting for CI of that fixing branch… just rebased yet again


-- 
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] [main] Upgrade important CI environment [airflow]

2026-07-11 Thread via GitHub


Lee-W commented on PR #69694:
URL: https://github.com/apache/airflow/pull/69694#issuecomment-495107

   Thanks, just rebased. Let's see how CI goes


-- 
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] [main] Upgrade important CI environment [airflow]

2026-07-11 Thread via GitHub


FrankYang0529 commented on PR #69694:
URL: https://github.com/apache/airflow/pull/69694#issuecomment-4949864721

   The CI error can be fixed by https://github.com/apache/airflow/pull/69755.
   
   
https://github.com/apache/airflow/actions/runs/29136631210/job/86503145941?pr=69694


-- 
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] [main] Upgrade important CI environment [airflow]

2026-07-08 Thread via GitHub


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

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

   
   Note: As of [Merging PRs targeted for Airflow 
3.X](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#merging-prs-targeted-for-airflow-3x)
   the committer who merges the PR is responsible for backporting the PRs that 
are bug fixes (generally speaking) to the maintenance branches.
   
   In matter of doubt please ask in 
[#release-management](https://apache-airflow.slack.com/archives/C03G9H97MM2) 
Slack channel.
   
   
   
   Status
   Branch
   Result
   
   
   ❌
   v3-3-test
   https://github.com/apache/airflow/commit/e7b8fa2129cf789a4e84198e8c08f670ad4f1548";>
   
   
   
   You can attempt to backport this manually by running:
   
   ```bash
   cherry_picker e7b8fa2 v3-3-test
   ```
   
   This should apply the commit to the v3-3-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
   ```
   
   If you don't have cherry-picker installed, see the [installation 
guide](https://github.com/apache/airflow/blob/main/dev/README.md#how-to-backport-pr-with-cherry-picker-cli).
   


-- 
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] [main] Upgrade important CI environment [airflow]

2026-07-08 Thread via GitHub


Lee-W merged PR #69445:
URL: https://github.com/apache/airflow/pull/69445


-- 
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] [main] Upgrade important CI environment [airflow]

2026-07-03 Thread via GitHub


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

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

   
   Note: As of [Merging PRs targeted for Airflow 
3.X](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#merging-prs-targeted-for-airflow-3x)
   the committer who merges the PR is responsible for backporting the PRs that 
are bug fixes (generally speaking) to the maintenance branches.
   
   In matter of doubt please ask in 
[#release-management](https://apache-airflow.slack.com/archives/C03G9H97MM2) 
Slack channel.
   
   
   
   Status
   Branch
   Result
   
   
   ❌
   v3-3-test
   https://github.com/apache/airflow/commit/1fa6b4f5693f0562603e4acbe0ca542fc1892f52";>
   
   
   
   You can attempt to backport this manually by running:
   
   ```bash
   cherry_picker 1fa6b4f v3-3-test
   ```
   
   This should apply the commit to the v3-3-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
   ```
   
   If you don't have cherry-picker installed, see the [installation 
guide](https://github.com/apache/airflow/blob/main/dev/README.md#how-to-backport-pr-with-cherry-picker-cli).
   


-- 
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] [main] Upgrade important CI environment [airflow]

2026-07-03 Thread via GitHub


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


-- 
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] [main] Upgrade important CI environment [airflow]

2026-06-30 Thread via GitHub


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

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

   
   Note: As of [Merging PRs targeted for Airflow 
3.X](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#merging-prs-targeted-for-airflow-3x)
   the committer who merges the PR is responsible for backporting the PRs that 
are bug fixes (generally speaking) to the maintenance branches.
   
   In matter of doubt please ask in 
[#release-management](https://apache-airflow.slack.com/archives/C03G9H97MM2) 
Slack channel.
   
   
   
   Status
   Branch
   Result
   
   
   ❌
   v3-3-test
   https://github.com/apache/airflow/commit/e0a1726aa586800ec65e2626b4d110b83ecc88fa";>
   
   
   
   You can attempt to backport this manually by running:
   
   ```bash
   cherry_picker e0a1726 v3-3-test
   ```
   
   This should apply the commit to the v3-3-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
   ```
   
   If you don't have cherry-picker installed, see the [installation 
guide](https://github.com/apache/airflow/blob/main/dev/README.md#how-to-backport-pr-with-cherry-picker-cli).
   


-- 
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] [main] Upgrade important CI environment [airflow]

2026-06-30 Thread via GitHub


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


-- 
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] [main] Upgrade important CI environment [airflow]

2026-06-26 Thread via GitHub


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

   
   `uv.lock` on `main` just moved via 
[#68780](https://github.com/apache/airflow/pull/68780) ("Bump zeep from 4.3.2 
to 4.3.3"), commit 
[`e6c1ae6`](https://github.com/apache/airflow/commit/e6c1ae67ac8cc20b416a38572479153cfb21395f)
 and this PR currently conflicts.
   
   Quickest fix:
   ```bash
   git fetch upstream main && git rebase upstream/main
   rm uv.lock && uv lock
   git add uv.lock && git rebase --continue
   git push --force-with-lease
   ```
   
   _Automated nudge — ignore if you're not ready to rebase. This comment is 
updated in place on future `uv.lock` bumps._


-- 
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] [main] Upgrade important CI environment [airflow]

2026-06-22 Thread via GitHub


Lee-W merged PR #68560:
URL: https://github.com/apache/airflow/pull/68560


-- 
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] [main] Upgrade important CI environment [airflow]

2026-06-17 Thread via GitHub


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

   
   `uv.lock` on `main` just moved via 
[#68400](https://github.com/apache/airflow/pull/68400) ("Bump 
`clickhouse-connect>=1.3.0`"), commit 
[`844a892`](https://github.com/apache/airflow/commit/844a892cb992c4e7637bfff203fc8f6742ceb3a2)
 and this PR currently conflicts.
   
   Quickest fix:
   ```bash
   git fetch upstream main && git rebase upstream/main
   rm uv.lock && uv lock
   git add uv.lock && git rebase --continue
   git push --force-with-lease
   ```
   
   _Automated nudge — ignore if you're not ready to rebase. This comment is 
updated in place on future `uv.lock` bumps._


-- 
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] [main] Upgrade important CI environment [airflow]

2026-06-12 Thread via GitHub


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


-- 
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] [main] Upgrade important CI environment [airflow]

2026-06-10 Thread via GitHub


bugraoz93 merged PR #68322:
URL: https://github.com/apache/airflow/pull/68322


-- 
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] [main] Upgrade important CI environment [airflow]

2026-06-08 Thread via GitHub


jscheffl merged PR #68209:
URL: https://github.com/apache/airflow/pull/68209


-- 
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] [main] Upgrade important CI environment [airflow]

2026-06-07 Thread via GitHub


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

   ### Backport failed to create: airflow-ctl/v0-1-test. View the failure log 
 Run 
details 
   
   Note: As of [Merging PRs targeted for Airflow 
3.X](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#merging-prs-targeted-for-airflow-3x)
   the committer who merges the PR is responsible for backporting the PRs that 
are bug fixes (generally speaking) to the maintenance branches.
   
   In matter of doubt please ask in 
[#release-management](https://apache-airflow.slack.com/archives/C03G9H97MM2) 
Slack channel.
   
   
   
   Status
   Branch
   Result
   
   
   ❌
   airflow-ctl/v0-1-test
   https://github.com/apache/airflow/commit/f636d83bd9559833667d0a582b06d4ddd75b0616";>
   
   
   
   You can attempt to backport this manually by running:
   
   ```bash
   cherry_picker f636d83 airflow-ctl/v0-1-test
   ```
   
   This should apply the commit to the airflow-ctl/v0-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
   ```
   
   If you don't have cherry-picker installed, see the [installation 
guide](https://github.com/apache/airflow/blob/main/dev/README.md#how-to-backport-pr-with-cherry-picker-cli).
   


-- 
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] [main] Upgrade important CI environment [airflow]

2026-06-07 Thread via GitHub


jscheffl commented on PR #68163:
URL: https://github.com/apache/airflow/pull/68163#issuecomment-4643605908

   One test is excessively long but not touching any of the changed PR, merging 
therefore.


-- 
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] [main] Upgrade important CI environment [airflow]

2026-06-07 Thread via GitHub


jscheffl commented on PR #68163:
URL: https://github.com/apache/airflow/pull/68163#issuecomment-4643608257

   No backport, will be maintained on 3.2 with a parallel pipeline


-- 
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] [main] Upgrade important CI environment [airflow]

2026-06-07 Thread via GitHub


jscheffl merged PR #68163:
URL: https://github.com/apache/airflow/pull/68163


-- 
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] [main] Upgrade important CI environment [airflow]

2026-06-07 Thread via GitHub


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

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

   
   Note: As of [Merging PRs targeted for Airflow 
3.X](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#merging-prs-targeted-for-airflow-3x)
   the committer who merges the PR is responsible for backporting the PRs that 
are bug fixes (generally speaking) to the maintenance branches.
   
   In matter of doubt please ask in 
[#release-management](https://apache-airflow.slack.com/archives/C03G9H97MM2) 
Slack channel.
   
   
   
   Status
   Branch
   Result
   
   
   ❌
   v3-2-test
   https://github.com/apache/airflow/commit/2f7e50f0b1df83745b1ff72b8596c694d335ec71";>
   
   
   
   You can attempt to backport this manually by running:
   
   ```bash
   cherry_picker 2f7e50f v3-2-test
   ```
   
   This should apply the commit to the v3-2-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
   ```
   
   If you don't have cherry-picker installed, see the [installation 
guide](https://github.com/apache/airflow/blob/main/dev/README.md#how-to-backport-pr-with-cherry-picker-cli).
   


-- 
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] [main] Upgrade important CI environment [airflow]

2026-06-07 Thread via GitHub


jscheffl merged PR #68062:
URL: https://github.com/apache/airflow/pull/68062


-- 
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] [main] Upgrade important CI environment [airflow]

2026-06-07 Thread via GitHub


jscheffl commented on PR #68062:
URL: https://github.com/apache/airflow/pull/68062#issuecomment-4642258381

   Java E2E test is broken atm ignote this being failing. See 
https://github.com/apache/airflow/pull/68161 - therefore merging if rest is 
green


-- 
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] [main] Upgrade important CI environment [airflow]

2026-06-07 Thread via GitHub


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

   
   `uv.lock` on `main` just moved via 
[#68105](https://github.com/apache/airflow/pull/68105) ("Bump pydantic-ai-slim 
to resolve dependabot"), commit 
[`db9c9cc`](https://github.com/apache/airflow/commit/db9c9cc94ded2f5b35833bde7049f816491723ea)
 and this PR currently conflicts.
   
   Quickest fix:
   ```bash
   git fetch upstream main && git rebase upstream/main
   rm uv.lock && uv lock
   git add uv.lock && git rebase --continue
   git push --force-with-lease
   ```
   
   _Automated nudge — ignore if you're not ready to rebase. This comment is 
updated in place on future `uv.lock` bumps._


-- 
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] [main] Upgrade important CI environment [airflow]

2026-06-05 Thread via GitHub


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

   > Exclude auto-generated REST API reference from docs spell-check #68114
   
   Likely fix https://github.com/apache/airflow/pull/68114
   


-- 
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] [main] Upgrade important CI environment [airflow]

2026-06-03 Thread via GitHub


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

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

   
   Note: As of [Merging PRs targeted for Airflow 
3.X](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#merging-prs-targeted-for-airflow-3x)
   the committer who merges the PR is responsible for backporting the PRs that 
are bug fixes (generally speaking) to the maintenance branches.
   
   In matter of doubt please ask in 
[#release-management](https://apache-airflow.slack.com/archives/C03G9H97MM2) 
Slack channel.
   
   
   
   Status
   Branch
   Result
   
   
   ❌
   v3-2-test
   https://github.com/apache/airflow/commit/19fa8ff584730363452d5743896ec587f8556474";>
   
   
   
   You can attempt to backport this manually by running:
   
   ```bash
   cherry_picker 19fa8ff v3-2-test
   ```
   
   This should apply the commit to the v3-2-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
   ```
   
   If you don't have cherry-picker installed, see the [installation 
guide](https://github.com/apache/airflow/blob/main/dev/README.md#how-to-backport-pr-with-cherry-picker-cli).
   


-- 
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] [main] Upgrade important CI environment [airflow]

2026-06-03 Thread via GitHub


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


-- 
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] [main] Upgrade important CI environment [airflow]

2026-06-01 Thread via GitHub


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


-- 
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] [main] Upgrade important CI environment [airflow]

2026-06-01 Thread via GitHub


jscheffl commented on PR #67860:
URL: https://github.com/apache/airflow/pull/67860#issuecomment-4596917603

   > Thanks for the fast turnaround on the Starlette 1.2.0 fallout — the root 
cause is exactly right (the TestClient prefers `httpx2` when it's importable, 
so responses become `httpx2.Response`).
   > 
   
   Great idea! Reverted bumping starlette but made tests compatible to both 
version streams. Keeps being flexible.


-- 
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] [main] Upgrade important CI environment [airflow]

2026-06-01 Thread via GitHub


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

   Thanks for the fast turnaround on the Starlette 1.2.0 fallout — the root 
cause is exactly right (the TestClient prefers `httpx2` when it's importable, 
so responses become `httpx2.Response`).
   
   One concern with pointing the tests *at* `httpx2` (`from httpx2 import 
Response`, `import httpx2`, `pytest.raises(httpx2.HTTPStatusError)`): it makes 
the tests **hard-depend on `httpx2` being installed**. `httpx2` is only present 
transitively via `providers-common-ai → pydantic-ai-slim → genai-prices`; a 
plain core sync doesn't pull it — `uv sync --project airflow-core` installs no 
`httpx2`. In any environment that collects these tests without `httpx2` 
present, `import httpx2` / `from httpx2 import Response` raises 
`ModuleNotFoundError` at import time. It works on the CI matrix that does pull 
`httpx2` (where it was failing), but it's more fragile than necessary and 
couples the test to which HTTP backend happens to be installed.
   
   `httpx2.Response` and `httpx.Response` share the same surface, and only the 
status code and body are part of the API contract — so the tests don't need to 
care which backend the TestClient used. Asserting on those is robust whether 
`httpx`, `httpx2`, or neither is installed. Proposing to revert the `httpx2` 
test edits and make the assertions backend-agnostic instead:
   
   **`test_dag_sources.py`** — keep the import on `httpx` and drop the brittle 
`isinstance` checks (the status/content/`Content-Type` assertions already cover 
the behaviour):
   
   ```diff
   -from httpx2 import Response
   +from httpx import Response
   @@
response: Response = test_client.get(f"{API_PREFIX}/{TEST_DAG_ID}", 
headers={"Accept": "text/plain"})
   -
   -assert isinstance(response, Response)
assert response.status_code == 200
assert dag_content == response.content.decode()
   @@
headers=headers,
)
   -assert isinstance(response, Response)
assert response.status_code == 200
assert response.json() == {
   ```
   
   **`test_xcoms.py`** — assert the status code instead of relying on the 
client's exception class (drops the `httpx2`/`httpx`/`contextlib` imports):
   
   ```diff
   -import contextlib
import logging
import urllib.parse
   -
   -import httpx
import pytest
   @@
@pytest.mark.parametrize(
   -("length", "err_context"),
   -[
   -pytest.param(20, contextlib.nullcontext(), id="20-success"),
   -pytest.param(2000, pytest.raises(httpx.HTTPStatusError), 
id="2000-too-long"),
   -],
   +("length", "expected_status"),
   +[
   +pytest.param(20, 201, id="20-success"),
   +pytest.param(2000, 400, id="2000-too-long"),
   +],
)
   -def test_xcom_set_downstream_of_mapped(self, client, 
create_task_instance, session, length, err_context):
   +def test_xcom_set_downstream_of_mapped(
   +self, client, create_task_instance, session, length, expected_status
   +):
...
   -with err_context:
   -response = client.post(..., params={"mapped_length": length})
   -response.raise_for_status()
   -task_map = session.scalars(...).one_or_none()
   -assert task_map.length == length
   +response = client.post(..., params={"mapped_length": length})
   +assert response.status_code == expected_status
   +if expected_status < 400:
   +task_map = session.scalars(...).one_or_none()
   +assert task_map.length == length
   ```
   
   (The `callback_runner.py` `# noqa` removal is fine as-is — no change needed 
there.)
   
   I verified this passes both **with `httpx2` installed** (the CI scenario 
that was failing) and without it. Happy to push it as a fix-up to this branch 
if you'd like — your call, it's your PR.
   
   ---
   Drafted-by: Claude Code (Opus 4.8); reviewed by @potiuk before posting
   


-- 
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] [main] Upgrade important CI environment [airflow]

2026-06-01 Thread via GitHub


jscheffl commented on PR #67860:
URL: https://github.com/apache/airflow/pull/67860#issuecomment-4596465209

   Re-opening to ensure full tests


-- 
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] [main] Upgrade important CI environment [airflow]

2026-06-01 Thread via GitHub


jscheffl closed pull request #67860: [main] Upgrade important CI environment
URL: https://github.com/apache/airflow/pull/67860


-- 
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] [main] Upgrade important CI environment [airflow]

2026-06-01 Thread via GitHub


jscheffl commented on PR #67860:
URL: https://github.com/apache/airflow/pull/67860#issuecomment-4596462570

   # Reviewer note:
   
   newest staröette >1.2.0 pulls httpx2 as test client which made tests fail. 
To prevent upper-limit starlette to <1.2.0 I bumped starlette to lower bound in 
this PR to >= 1.2.0.
   This would ensure tests are still working... whereas I assume (untested 
though) that core still works with old and new version... but not tested.
   
   Is it OK to bump or shall we leave it purely to uv lock?


-- 
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] [main] Upgrade important CI environment [airflow]

2026-06-01 Thread via GitHub


jscheffl commented on PR #67860:
URL: https://github.com/apache/airflow/pull/67860#issuecomment-4596281347

   Mhm, starlette 1.2.0 somehow seems to break something, investigating. If no 
easy fix will pin starlette below 1.2.0


-- 
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] [main] Upgrade important CI environment [airflow]

2026-06-01 Thread via GitHub


jscheffl commented on PR #67860:
URL: https://github.com/apache/airflow/pull/67860#issuecomment-4596193858

   Haha, ruff is getting smarter every release :-D
   
   https://github.com/user-attachments/assets/45addd29-de2c-4981-91fd-694eb95a85c4";
 />
   


-- 
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] [main] Upgrade important CI environment [airflow]

2026-06-01 Thread via GitHub


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

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

   
   Note: As of [Merging PRs targeted for Airflow 
3.X](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#merging-prs-targeted-for-airflow-3x)
   the committer who merges the PR is responsible for backporting the PRs that 
are bug fixes (generally speaking) to the maintenance branches.
   
   In matter of doubt please ask in 
[#release-management](https://apache-airflow.slack.com/archives/C03G9H97MM2) 
Slack channel.
   
   
   
   Status
   Branch
   Result
   
   
   ❌
   v3-2-test
   https://github.com/apache/airflow/commit/24523eae721d5dcf26cc24c89ecc7634b27e62f9";>
   
   
   
   You can attempt to backport this manually by running:
   
   ```bash
   cherry_picker 24523ea v3-2-test
   ```
   
   This should apply the commit to the v3-2-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
   ```
   
   If you don't have cherry-picker installed, see the [installation 
guide](https://github.com/apache/airflow/blob/main/dev/README.md#how-to-backport-pr-with-cherry-picker-cli).
   


-- 
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] [main] Upgrade important CI environment [airflow]

2026-06-01 Thread via GitHub


jscheffl merged PR #67827:
URL: https://github.com/apache/airflow/pull/67827


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-30 Thread via GitHub


jscheffl merged PR #67779:
URL: https://github.com/apache/airflow/pull/67779


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-30 Thread via GitHub


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

   > > @bugraoz93 @potiuk @gopidesupavan THanks for (earlier) review - seems 
static checks are now OK - still OK to merge from your view?
   > 
   > As long as CI is green - absolutely :D
   
   
   +1, thanks Jens! :)


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-30 Thread via GitHub


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

   > @bugraoz93 @potiuk @gopidesupavan THanks for (earlier) review - seems 
static checks are now OK - still OK to merge from your view?
   
   As long as CI is green - absolutely :D


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-30 Thread via GitHub


jscheffl commented on PR #67779:
URL: https://github.com/apache/airflow/pull/67779#issuecomment-4584881816

   @bugraoz93 @potiuk @gopidesupavan THanks for (earlier) review - seems static 
checks are now OK - still OK to merge from your view?


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-30 Thread via GitHub


jscheffl commented on PR #67779:
URL: https://github.com/apache/airflow/pull/67779#issuecomment-4584141863

   > I am not sure what is wrong but multiple re-ruins and also a rebase did 
not help, failing in `Bind for 0.0.0.0:12322 failed: port is already allocated` 
- this is the SSH Port of the docker. Error is raised in prek - looks like if 
docker is not properly terminated? Has anybody seen this before?
   
   My Agent (and me) have the suspect that the new prek 0.4.2 adds more 
paralellism in checks which generates a race of different Breeze containers 
running concurrnetly. Will attempt to fix it...
   
   FYI @j178 


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-30 Thread via GitHub


jscheffl commented on PR #67779:
URL: https://github.com/apache/airflow/pull/67779#issuecomment-4584078485

   I am not sure what is wrong but multiple re-ruins and also a rebase did not 
help, failing in `Bind for 0.0.0.0:12322 failed: port is already allocated` - 
this is the SSH Port of the docker. Error is raised in prek - looks like if 
docker is not properly terminated? Has anybody seen this before?


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-30 Thread via GitHub


jscheffl commented on PR #67779:
URL: https://github.com/apache/airflow/pull/67779#issuecomment-4583024901

   See https://github.com/SAP/swagger-plugin-for-sphinx/issues/518


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-29 Thread via GitHub


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

   ### Backport failed to create: chart/v1-2x-test. View the failure log  Run details 

   
   Note: As of [Merging PRs targeted for Airflow 
3.X](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#merging-prs-targeted-for-airflow-3x)
   the committer who merges the PR is responsible for backporting the PRs that 
are bug fixes (generally speaking) to the maintenance branches.
   
   In matter of doubt please ask in 
[#release-management](https://apache-airflow.slack.com/archives/C03G9H97MM2) 
Slack channel.
   
   
   
   Status
   Branch
   Result
   
   
   ❌
   chart/v1-2x-test
   https://github.com/apache/airflow/commit/d68d9e2c311e55ac23bc8d3c9d0a62c7b307c50a";>
   
   
   
   You can attempt to backport this manually by running:
   
   ```bash
   cherry_picker d68d9e2 chart/v1-2x-test
   ```
   
   This should apply the commit to the chart/v1-2x-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
   ```
   
   If you don't have cherry-picker installed, see the [installation 
guide](https://github.com/apache/airflow/blob/main/dev/README.md#how-to-backport-pr-with-cherry-picker-cli).
   


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-29 Thread via GitHub


jscheffl merged PR #67686:
URL: https://github.com/apache/airflow/pull/67686


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-29 Thread via GitHub


jscheffl commented on code in PR #67686:
URL: https://github.com/apache/airflow/pull/67686#discussion_r3322953675


##
chart/values.yaml:
##
@@ -102,7 +102,7 @@ images:
 pullPolicy: IfNotPresent
   statsd:
 repository: quay.io/prometheus/statsd-exporter
-tag: v0.29.0
+tag: v0-distroless

Review Comment:
   ```suggestion
   tag: v0.30.0
   ```



-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-29 Thread via GitHub


jscheffl commented on code in PR #67686:
URL: https://github.com/apache/airflow/pull/67686#discussion_r3322949036


##
chart/values.schema.json:
##
@@ -968,7 +968,7 @@
 "tag": {
 "description": "The StatsD image tag.",
 "type": "string",
-"default": "v0.29.0"
+"default": "v0-distroless"

Review Comment:
   Same time also one with version number was pushed:
   ```suggestion
   "default": "v0.30.0"
   ```



-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-29 Thread via GitHub


jscheffl commented on code in PR #67686:
URL: https://github.com/apache/airflow/pull/67686#discussion_r3322943197


##
chart/values.schema.json:
##
@@ -968,7 +968,7 @@
 "tag": {
 "description": "The StatsD image tag.",
 "type": "string",
-"default": "v0.29.0"
+"default": "v0-distroless"

Review Comment:
   Mhm, that looks a bit strange/unintended?
   Does somebody know where and why this was selected in the past? Image w/o 
version number smells like "latest" and not preferrable



-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-27 Thread via GitHub


jscheffl merged PR #67613:
URL: https://github.com/apache/airflow/pull/67613


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-27 Thread via GitHub


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

   ### Backport failed to create: airflow-ctl/v0-1-test. View the failure log 
 Run 
details 
   
   Note: As of [Merging PRs targeted for Airflow 
3.X](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#merging-prs-targeted-for-airflow-3x)
   the committer who merges the PR is responsible for backporting the PRs that 
are bug fixes (generally speaking) to the maintenance branches.
   
   In matter of doubt please ask in 
[#release-management](https://apache-airflow.slack.com/archives/C03G9H97MM2) 
Slack channel.
   
   
   
   Status
   Branch
   Result
   
   
   ❌
   airflow-ctl/v0-1-test
   https://github.com/apache/airflow/commit/a2d5fa9c436ca04050ef4bcbd15e6cf2d68a692f";>
   
   
   
   You can attempt to backport this manually by running:
   
   ```bash
   cherry_picker a2d5fa9 airflow-ctl/v0-1-test
   ```
   
   This should apply the commit to the airflow-ctl/v0-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
   ```
   
   If you don't have cherry-picker installed, see the [installation 
guide](https://github.com/apache/airflow/blob/main/dev/README.md#how-to-backport-pr-with-cherry-picker-cli).
   


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-27 Thread via GitHub


jscheffl merged PR #67593:
URL: https://github.com/apache/airflow/pull/67593


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-25 Thread via GitHub


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


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-25 Thread via GitHub


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

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

   
   Note: As of [Merging PRs targeted for Airflow 
3.X](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#merging-prs-targeted-for-airflow-3x)
   the committer who merges the PR is responsible for backporting the PRs that 
are bug fixes (generally speaking) to the maintenance branches.
   
   In matter of doubt please ask in 
[#release-management](https://apache-airflow.slack.com/archives/C03G9H97MM2) 
Slack channel.
   
   
   
   Status
   Branch
   Result
   
   
   ❌
   v3-2-test
   https://github.com/apache/airflow/commit/f3f7e909b0809fa3abedb763443b8079d8921c1e";>
   
   
   
   You can attempt to backport this manually by running:
   
   ```bash
   cherry_picker f3f7e90 v3-2-test
   ```
   
   This should apply the commit to the v3-2-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
   ```
   
   If you don't have cherry-picker installed, see the [installation 
guide](https://github.com/apache/airflow/blob/main/dev/README.md#how-to-backport-pr-with-cherry-picker-cli).
   


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-25 Thread via GitHub


jscheffl merged PR #67313:
URL: https://github.com/apache/airflow/pull/67313


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-24 Thread via GitHub


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

   
   `uv.lock` on `main` just moved via 
[#67383](https://github.com/apache/airflow/pull/67383) ("Cleanup 
older/outddated uv cooldown exception"), commit 
[`62845dd`](https://github.com/apache/airflow/commit/62845dd743b5e12d7dfd81f92ae5a9767f835fa1)
 and this PR currently conflicts.
   
   Quickest fix:
   ```bash
   git fetch upstream main && git rebase upstream/main
   rm uv.lock && uv lock
   git add uv.lock && git rebase --continue
   git push --force-with-lease
   ```
   
   _Automated nudge — ignore if you're not ready to rebase. This comment is 
updated in place on future `uv.lock` bumps._


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-23 Thread via GitHub


jscheffl commented on PR #67313:
URL: https://github.com/apache/airflow/pull/67313#issuecomment-4526027398

   @dependabot rebase


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-20 Thread via GitHub


jscheffl commented on PR #67232:
URL: https://github.com/apache/airflow/pull/67232#issuecomment-4502525333

   No backport, there is another automated pipeline on v3-2-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] [main] Upgrade important CI environment [airflow]

2026-05-20 Thread via GitHub


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

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

   
   Note: As of [Merging PRs targeted for Airflow 
3.X](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#merging-prs-targeted-for-airflow-3x)
   the committer who merges the PR is responsible for backporting the PRs that 
are bug fixes (generally speaking) to the maintenance branches.
   
   In matter of doubt please ask in 
[#release-management](https://apache-airflow.slack.com/archives/C03G9H97MM2) 
Slack channel.
   
   
   
   Status
   Branch
   Result
   
   
   ❌
   v3-2-test
   https://github.com/apache/airflow/commit/6b64a621be4c376bf899294e144e7693ae68148d";>
   
   
   
   You can attempt to backport this manually by running:
   
   ```bash
   cherry_picker 6b64a62 v3-2-test
   ```
   
   This should apply the commit to the v3-2-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
   ```
   
   If you don't have cherry-picker installed, see the [installation 
guide](https://github.com/apache/airflow/blob/main/dev/README.md#how-to-backport-pr-with-cherry-picker-cli).
   


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-20 Thread via GitHub


jscheffl merged PR #67232:
URL: https://github.com/apache/airflow/pull/67232


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-18 Thread via GitHub


jscheffl commented on PR #67093:
URL: https://github.com/apache/airflow/pull/67093#issuecomment-4482418494

   Oh, no backport, assuming another automated job on v3.2.tet running in 
parallel...


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-18 Thread via GitHub


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

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

   
   Note: As of [Merging PRs targeted for Airflow 
3.X](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#merging-prs-targeted-for-airflow-3x)
   the committer who merges the PR is responsible for backporting the PRs that 
are bug fixes (generally speaking) to the maintenance branches.
   
   In matter of doubt please ask in 
[#release-management](https://apache-airflow.slack.com/archives/C03G9H97MM2) 
Slack channel.
   
   
   
   Status
   Branch
   Result
   
   
   ❌
   v3-2-test
   https://github.com/apache/airflow/commit/b465693c80e518bc99090486e10be3c60581d55c";>
   
   
   
   You can attempt to backport this manually by running:
   
   ```bash
   cherry_picker b465693 v3-2-test
   ```
   
   This should apply the commit to the v3-2-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
   ```
   
   If you don't have cherry-picker installed, see the [installation 
guide](https://github.com/apache/airflow/blob/main/dev/README.md#how-to-backport-pr-with-cherry-picker-cli).
   


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-18 Thread via GitHub


jscheffl merged PR #67093:
URL: https://github.com/apache/airflow/pull/67093


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-15 Thread via GitHub


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

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

   
   Note: As of [Merging PRs targeted for Airflow 
3.X](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#merging-prs-targeted-for-airflow-3x)
   the committer who merges the PR is responsible for backporting the PRs that 
are bug fixes (generally speaking) to the maintenance branches.
   
   In matter of doubt please ask in 
[#release-management](https://apache-airflow.slack.com/archives/C03G9H97MM2) 
Slack channel.
   
   
   
   Status
   Branch
   Result
   
   
   ❌
   v3-2-test
   https://github.com/apache/airflow/commit/0c4c1f81ac6f90dbfde3d5cd63cfeabd7a47";>
   
   
   
   You can attempt to backport this manually by running:
   
   ```bash
   cherry_picker 0c4c1f8 v3-2-test
   ```
   
   This should apply the commit to the v3-2-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
   ```
   
   If you don't have cherry-picker installed, see the [installation 
guide](https://github.com/apache/airflow/blob/main/dev/README.md#how-to-backport-pr-with-cherry-picker-cli).
   


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-15 Thread via GitHub


Lee-W merged PR #66980:
URL: https://github.com/apache/airflow/pull/66980


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-14 Thread via GitHub


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

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

   
   Note: As of [Merging PRs targeted for Airflow 
3.X](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#merging-prs-targeted-for-airflow-3x)
   the committer who merges the PR is responsible for backporting the PRs that 
are bug fixes (generally speaking) to the maintenance branches.
   
   In matter of doubt please ask in 
[#release-management](https://apache-airflow.slack.com/archives/C03G9H97MM2) 
Slack channel.
   
   
   
   Status
   Branch
   Result
   
   
   ❌
   v3-2-test
   https://github.com/apache/airflow/commit/8a76a8926e0d592680e48539339a1a01601565d8";>
   
   
   
   You can attempt to backport this manually by running:
   
   ```bash
   cherry_picker 8a76a89 v3-2-test
   ```
   
   This should apply the commit to the v3-2-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
   ```
   
   If you don't have cherry-picker installed, see the [installation 
guide](https://github.com/apache/airflow/blob/main/dev/README.md#how-to-backport-pr-with-cherry-picker-cli).
   


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-14 Thread via GitHub


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

   ### Backport failed to create: airflow-ctl/v0-1-test. View the failure log 
 Run 
details 
   
   Note: As of [Merging PRs targeted for Airflow 
3.X](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#merging-prs-targeted-for-airflow-3x)
   the committer who merges the PR is responsible for backporting the PRs that 
are bug fixes (generally speaking) to the maintenance branches.
   
   In matter of doubt please ask in 
[#release-management](https://apache-airflow.slack.com/archives/C03G9H97MM2) 
Slack channel.
   
   
   
   Status
   Branch
   Result
   
   
   ❌
   airflow-ctl/v0-1-test
   https://github.com/apache/airflow/commit/8a76a8926e0d592680e48539339a1a01601565d8";>
   
   
   
   You can attempt to backport this manually by running:
   
   ```bash
   cherry_picker 8a76a89 airflow-ctl/v0-1-test
   ```
   
   This should apply the commit to the airflow-ctl/v0-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
   ```
   
   If you don't have cherry-picker installed, see the [installation 
guide](https://github.com/apache/airflow/blob/main/dev/README.md#how-to-backport-pr-with-cherry-picker-cli).
   


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-14 Thread via GitHub


jscheffl merged PR #66843:
URL: https://github.com/apache/airflow/pull/66843


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-12 Thread via GitHub


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

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

   
   Note: As of [Merging PRs targeted for Airflow 
3.X](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#merging-prs-targeted-for-airflow-3x)
   the committer who merges the PR is responsible for backporting the PRs that 
are bug fixes (generally speaking) to the maintenance branches.
   
   In matter of doubt please ask in 
[#release-management](https://apache-airflow.slack.com/archives/C03G9H97MM2) 
Slack channel.
   
   
   
   Status
   Branch
   Result
   
   
   ❌
   v3-2-test
   https://github.com/apache/airflow/commit/25bdaf417b40b0645f3878916397f2b86dcb9a1a";>
   
   
   
   You can attempt to backport this manually by running:
   
   ```bash
   cherry_picker 25bdaf4 v3-2-test
   ```
   
   This should apply the commit to the v3-2-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
   ```
   
   If you don't have cherry-picker installed, see the [installation 
guide](https://github.com/apache/airflow/blob/main/dev/README.md#how-to-backport-pr-with-cherry-picker-cli).
   


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-12 Thread via GitHub


jscheffl merged PR #66700:
URL: https://github.com/apache/airflow/pull/66700


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-10 Thread via GitHub


jscheffl commented on PR #66631:
URL: https://github.com/apache/airflow/pull/66631#issuecomment-4415512439

   Repeating same in https://github.com/apache/airflow/pull/66654


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-09 Thread via GitHub


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

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

   
   Note: As of [Merging PRs targeted for Airflow 
3.X](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#merging-prs-targeted-for-airflow-3x)
   the committer who merges the PR is responsible for backporting the PRs that 
are bug fixes (generally speaking) to the maintenance branches.
   
   In matter of doubt please ask in 
[#release-management](https://apache-airflow.slack.com/archives/C03G9H97MM2) 
Slack channel.
   
   
   
   Status
   Branch
   Result
   
   
   ❌
   v3-2-test
   https://github.com/apache/airflow/commit/1aff9b693432425beace408afe1e03b06736cc77";>
   
   
   
   You can attempt to backport this manually by running:
   
   ```bash
   cherry_picker 1aff9b6 v3-2-test
   ```
   
   This should apply the commit to the v3-2-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
   ```
   
   If you don't have cherry-picker installed, see the [installation 
guide](https://github.com/apache/airflow/blob/main/dev/README.md#how-to-backport-pr-with-cherry-picker-cli).
   


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-09 Thread via GitHub


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


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-09 Thread via GitHub


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

   
   `uv.lock` on `main` just moved via 
[#66600](https://github.com/apache/airflow/pull/66600) ("[main] CI: Upgrade 
important CI environment"), commit 
[`8a55076`](https://github.com/apache/airflow/commit/8a5507625be45161385a32be756633f66a65a5c5)
 and this PR currently conflicts.
   
   Quickest fix:
   ```bash
   git fetch upstream main && git rebase upstream/main
   rm uv.lock && uv lock
   git add uv.lock && git rebase --continue
   git push --force-with-lease
   ```
   
   _Automated nudge — ignore if you're not ready to rebase. This comment is 
updated in place on future `uv.lock` bumps._


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-08 Thread via GitHub


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

   recreated https://github.com/apache/airflow/pull/66600 after fixing the 
alpine bump


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-08 Thread via GitHub


potiuk closed pull request #66580: [main] Upgrade important CI environment
URL: https://github.com/apache/airflow/pull/66580


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-08 Thread via GitHub


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

   closing to redo it.


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-08 Thread via GitHub


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

   This auto-bump picked Alpine's daily-edge tag `20260127` over the `3.23` 
release. Root cause is in 
`scripts/ci/prek/upgrade_important_versions.py::get_latest_image_version` — it 
used `packaging.version.Version()` parse-success as the "is this a release 
tag?" predicate, but PEP 440 happily parses `Version("20260127")` as a valid 
single-component version that sorts above `Version("3.23")`. So when Alpine's 
daily edge tag appeared in the Docker Hub `last_updated`-ordered tag list, the 
bumper selected it as "latest".
   
   Fix in #66588: pre-filter date-shaped tags via regex (`v?\d{8}(\.\d+)?`), 
plus a sanity guard rejecting any parsed `Version` with `major >= 1`, plus 
`edge` added to the floating-tag skiplist. Once that lands, the next auto-bump 
run produces `alpine:3.23.5` instead of the daily date stamp.
   
   This PR's `alpine:20260127` line should revert back to `alpine:3.23` (or 
`3.23.5`, whichever is current) once #66588 is in. Easiest path is to close 
this and let the next scheduled bumper run produce a clean replacement, but 
updating the alpine line in place works too.
   
   ---
   Drafted-by: Claude Opus 4.7 (1M context); reviewed by @potiuk before posting
   


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-08 Thread via GitHub


potiuk commented on code in PR #66580:
URL: https://github.com/apache/airflow/pull/66580#discussion_r3207359746


##
dev/breeze/src/airflow_breeze/commands/kubernetes_commands.py:
##
@@ -715,8 +715,8 @@ def _upload_k8s_image(python: str, kubernetes_version: str, 
output: Output | Non
 # turn the scheduled K8s test job red. Auto-bumped by
 # scripts/ci/prek/upgrade_important_versions.py.
 K8S_TEST_IMAGES_TO_PRELOAD: tuple[str, ...] = (
-"alpine:3.23",  # xcom_sidecar default in providers/cncf/kubernetes
-"busybox:1.37",  # busybox-based system tests in kubernetes-tests/
+"alpine:20260127",  # xcom_sidecar default in providers/cncf/kubernetes
+"busybox:1.37.0",  # busybox-based system tests in kubernetes-tests/

Review Comment:
   Upgrade script apparently takes into account also daily tags for alpine 
rather than only released ones... Let me fix it :)



-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-08 Thread via GitHub


amoghrajesh commented on code in PR #66580:
URL: https://github.com/apache/airflow/pull/66580#discussion_r3207245568


##
dev/breeze/src/airflow_breeze/commands/kubernetes_commands.py:
##
@@ -715,8 +715,8 @@ def _upload_k8s_image(python: str, kubernetes_version: str, 
output: Output | Non
 # turn the scheduled K8s test job red. Auto-bumped by
 # scripts/ci/prek/upgrade_important_versions.py.
 K8S_TEST_IMAGES_TO_PRELOAD: tuple[str, ...] = (
-"alpine:3.23",  # xcom_sidecar default in providers/cncf/kubernetes
-"busybox:1.37",  # busybox-based system tests in kubernetes-tests/
+"alpine:20260127",  # xcom_sidecar default in providers/cncf/kubernetes
+"busybox:1.37.0",  # busybox-based system tests in kubernetes-tests/

Review Comment:
   Something wrong w the diff here?



-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-06 Thread via GitHub


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


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-06 Thread via GitHub


potiuk closed pull request #66456: [main] Upgrade important CI environment
URL: https://github.com/apache/airflow/pull/66456


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-06 Thread via GitHub


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

   Rebase is not enough... We need to manually run it now.


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-06 Thread via GitHub


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

   rebased to account for the azure fix in main


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-04 Thread via GitHub


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

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

   
   Note: As of [Merging PRs targeted for Airflow 
3.X](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#merging-prs-targeted-for-airflow-3x)
   the committer who merges the PR is responsible for backporting the PRs that 
are bug fixes (generally speaking) to the maintenance branches.
   
   In matter of doubt please ask in 
[#release-management](https://apache-airflow.slack.com/archives/C03G9H97MM2) 
Slack channel.
   
   
   
   Status
   Branch
   Result
   
   
   ❌
   v3-2-test
   https://github.com/apache/airflow/commit/6f306eb7809254b8ca4b83ff0d3154313bc38a6c";>
   
   
   
   You can attempt to backport this manually by running:
   
   ```bash
   cherry_picker 6f306eb v3-2-test
   ```
   
   This should apply the commit to the v3-2-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
   ```
   
   If you don't have cherry-picker installed, see the [installation 
guide](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#how-to-backport-pr-with-cherry-picker-cli).
   


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-04 Thread via GitHub


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

   ### Backport failed to create: airflow-ctl/v0-1-test. View the failure log 
 Run 
details 
   
   Note: As of [Merging PRs targeted for Airflow 
3.X](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#merging-prs-targeted-for-airflow-3x)
   the committer who merges the PR is responsible for backporting the PRs that 
are bug fixes (generally speaking) to the maintenance branches.
   
   In matter of doubt please ask in 
[#release-management](https://apache-airflow.slack.com/archives/C03G9H97MM2) 
Slack channel.
   
   
   
   Status
   Branch
   Result
   
   
   ❌
   airflow-ctl/v0-1-test
   https://github.com/apache/airflow/commit/6f306eb7809254b8ca4b83ff0d3154313bc38a6c";>
   
   
   
   You can attempt to backport this manually by running:
   
   ```bash
   cherry_picker 6f306eb airflow-ctl/v0-1-test
   ```
   
   This should apply the commit to the airflow-ctl/v0-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
   ```
   
   If you don't have cherry-picker installed, see the [installation 
guide](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#how-to-backport-pr-with-cherry-picker-cli).
   


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-04 Thread via GitHub


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


-- 
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] [main] Upgrade important CI environment [airflow]

2026-05-01 Thread via GitHub


potiuk closed pull request #66187: [main] Upgrade important CI environment
URL: https://github.com/apache/airflow/pull/66187


-- 
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] [main] Upgrade important CI environment [airflow]

2026-04-29 Thread via GitHub


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

   Holding this PR until the global 4-day cooldown lifts for uv 0.11.8.
   
   Background: #66042 bumped uv to 0.11.8 manually with a temporary `uv = "12 
hours"` cooldown override under `[tool.uv.exclude-newer-package]` and 
`[tool.uv.pip.exclude-newer-package]` in `pyproject.toml` (flagged `REMOVE BY 
2026-05-01`) so the freshly-published 0.11.8 could be adopted as the floor 
without waiting on the project-wide window. After rebasing this PR onto current 
main, the bot's pre-cooldown resolution still pins uv to 0.11.7, which would 
now be a downgrade.
   
   Plan:
   
   1. Wait until the 4-day cooldown has passed for uv 0.11.8 (≈ 2026-05-01).
   2. Re-run the upgrade bot so the resolution picks 0.11.8 (or whatever is 
then latest outside cooldown) cleanly.
   3. Remove the `uv = "12 hours"` overrides in 
`[tool.uv.exclude-newer-package]` and `[tool.uv.pip.exclude-newer-package]` — 
redundant once the global window covers 0.11.8.
   4. Proceed with the normal review/merge.
   
   Leaving as draft in the meantime.
   
   ---
   Drafted-by: Claude Code (Opus 4.7); reviewed by @potiuk before posting


-- 
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] [main] Upgrade important CI environment [airflow]

2026-04-29 Thread via GitHub


Lee-W commented on code in PR #66068:
URL: https://github.com/apache/airflow/pull/66068#discussion_r3159544493


##
Dockerfile.ci:
##
@@ -1825,7 +1825,7 @@ COPY --from=scripts common.sh install_packaging_tools.sh 
install_additional_depe
 # Also use `force pip` label on your PR to swap all places we use `uv` to `pip`
 ARG AIRFLOW_PIP_VERSION=26.0.1
 # ARG AIRFLOW_PIP_VERSION="git+https://github.com/pypa/pip.git@main";
-ARG AIRFLOW_UV_VERSION=0.11.8
+ARG AIRFLOW_UV_VERSION=0.11.7

Review Comment:
   According to discussion in #contributors, we want to use uv==0.11.8



-- 
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] [main] Upgrade important CI environment [airflow]

2026-04-27 Thread via GitHub


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


-- 
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] [main] Upgrade important CI environment [airflow]

2026-04-27 Thread via GitHub


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

   ### Backport failed to create: airflow-ctl/v0-1-test. View the failure log 
 Run 
details 
   
   Note: As of [Merging PRs targeted for Airflow 
3.X](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#merging-prs-targeted-for-airflow-3x)
   the committer who merges the PR is responsible for backporting the PRs that 
are bug fixes (generally speaking) to the maintenance branches.
   
   In matter of doubt please ask in 
[#release-management](https://apache-airflow.slack.com/archives/C03G9H97MM2) 
Slack channel.
   
   
   
   Status
   Branch
   Result
   
   
   ❌
   airflow-ctl/v0-1-test
   https://github.com/apache/airflow/commit/29477eaa6f499762d97bbc64ff55b756ccec454f";>
   
   
   
   You can attempt to backport this manually by running:
   
   ```bash
   cherry_picker 29477ea airflow-ctl/v0-1-test
   ```
   
   This should apply the commit to the airflow-ctl/v0-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
   ```
   
   If you don't have cherry-picker installed, see the [installation 
guide](https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#how-to-backport-pr-with-cherry-picker-cli).
   


-- 
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] [main] Upgrade important CI environment [airflow]

2026-04-24 Thread via GitHub


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


-- 
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]



  1   2   3   4   >