Skip to content

[main] Upgrade important CI environment - #69694

Merged
Lee-W merged 1 commit into
mainfrom
ci-upgrade-main
Jul 16, 2026
Merged

[main] Upgrade important CI environment#69694
Lee-W merged 1 commit into
mainfrom
ci-upgrade-main

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

This PR upgrades important dependencies of the CI environment.

@FrankYang0529

Copy link
Copy Markdown
Member

@Lee-W

Copy link
Copy Markdown
Member

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

@Lee-W

Copy link
Copy Markdown
Member

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

Comment threaduv.lock Outdated
@FrankYang0529

FrankYang0529 commented Jul 13, 2026

Copy link
Copy Markdown
Member

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

https://github.com/apache/airflow/actions/runs/29196580674/job/86661835233

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(
  1. rich 13.9.4 → 14.3.4

https://github.com/apache/airflow/actions/runs/29196580674/job/86661835522

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.

@Lee-W
Lee-W marked this pull request as ready for review July 15, 2026 06:57
@github-actions

github-actionsBot commented Jul 15, 2026

Copy link
Copy Markdown
ContributorAuthor

uv.lock on main just moved via #69887 ("Add pydantic-ai capability matrix references doc to Common AI"), commit b6ae668 and this PR currently conflicts.

Quickest fix:

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.

@FrankYang0529

Copy link
Copy Markdown
Member

Fix mypy 2.2.0 check.

#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)

@Lee-W

Copy link
Copy Markdown
Member

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

@Lee-W
Lee-W merged commit c8d313a into mainJul 16, 2026
304 checks passed
@Lee-W
Lee-W deleted the ci-upgrade-main branch July 16, 2026 09:52
@github-actions

Copy link
Copy Markdown
ContributorAuthor

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

Note: As of Merging PRs targeted for Airflow 3.X
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 Slack channel.

StatusBranchResult
v3-3-testCommit Link

You can attempt to backport this manually by running:

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:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

@FrankYang0529@Lee-W@bugraoz93@amoghrajesh@henry3260