Uh oh!
There was an error while loading. Please reload this page.
[main] Upgrade important CI environment - #68933
Merged
Merged
Conversation
Lee-W
approved these changes
Jun 24, 2026
github-actionsBotforce-pushed
the
ci-upgrade-main
branch
from
June 26, 2026 07:31
3b1e17c to
a037becCompareLee-W
approved these changes
Jun 26, 2026
Lee-W
marked this pull request as ready for review
June 26, 2026 07:39
Lee-W
requested review from
amoghrajesh, ashb, bugraoz93, choo121600, ephraimbuddy, gopidesupavan, jason810496, jedcunningham, jscheffl, potiuk and vatsrahul1001
as code ownersJune 26, 2026 07:39
amoghrajesh
approved these changes
Jun 26, 2026
ContributorAuthor
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-leaseAutomated nudge — ignore if you're not ready to rebase. This comment is updated in place on future |
github-actionsBotforce-pushed
the
ci-upgrade-main
branch
from
June 29, 2026 08:00
30a4c0b to
ff38c20CompareLee-W
marked this pull request as ready for review
June 29, 2026 08:09
This was referenced Jun 29, 2026
Lee-W
requested review from
Fokko, dheerajturaga, eladkal, josh-fell and o-nikolas
as code ownersJune 30, 2026 11:08
Regenerating the lockfile for the CI tooling bump also pulled two major provider-library upgrades that the bump was never meant to carry: pydantic-ai 1.x to 2.x (which changed the agent instrumentation API and breaks common.ai) and pyexasol 1.x to 2.x (whose stricter types break the exasol hook). Capping both to 1.x keeps this PR a pure tooling upgrade; the major-version migrations are tracked separately (#69122, #69123). The new zizmor 1.26.1 ref-version-mismatch audit also flagged the apache/infrastructure-actions pin, which is branch-tracked and pinned by SHA with a "# main" comment on purpose; scope that audit off for that file.
Committed index.rst files drifted from generated/provider_dependencies.json after recent cross-provider dependency additions (e.g. common.compat). CI's prepare-provider-documentation step regenerates these, so the stale docs must be synced for it to pass.
The earlier regeneration ran through a cached uvx-built Breeze that predated the cross-provider extras filtering, so the provider index pages still listed required cross-provider dependencies as optional installable extras. CI rebuilds Breeze from source and filters them out, which made the update-providers-build-files hook keep rewriting the pages and fail the static checks. Regenerated with `uvx --no-cache` so the committed pages match the canonical Breeze output.
Uh oh!
There was an error while loading. Please reload this page.
ContributorAuthor
Backport failed to create: v3-3-test. View the failure log Run detailsNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
You can attempt to backport this manually by running: cherry_picker e0a1726 v3-3-testThis should apply the commit to the v3-3-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continueIf you don't have cherry-picker installed, see the installation guide. |
This was referenced Jul 1, 2026
Open
75 tasks
1 task
joseph-bergin added a commit
to joseph-bergin/airflow
that referenced
this pull request
Aug 27, 2026
pyexasol 2.x ships type information, which surfaced six mypy errors in the exasol hook and forced the `pyexasol>=0.26.0,<2` cap added in apache#68933. Adapt the hook to the driver's real contract: - `get_conn` reused one local for both the Airflow `Connection` and the `ExaConnection` returned by `pyexasol.connect`. Use separate names. - `ExaConnection.execute`/`export_to_pandas` take `query_params: dict | None` and render named placeholders via `format(query, **query_params)`, so a positional sequence has always raised `TypeError: argument after ** must be a mapping`. Normalize mappings to `dict` and reject sequences up front with a message that names the fix. - `execute` runs exactly one statement, so the `str | list[str]` that `DbApiHook` allows was never executable here. Reject lists and point at `run()`, which does handle them. Both rejected paths were already broken against a real Exasol; only the error message changes. `test_run_with_parameters` passed a tuple and passed only because the connection is mocked, so it now uses a mapping, with new coverage for mapping normalization and for both rejections. Closes: apache#69123
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR upgrades important dependencies of the CI environment.