Skip to content

CI: Upgrade important CI environment#64744

Merged
potiuk merged 7 commits intoapache:mainfrom
astronomer:ci-upgrade-b91394aa4c
Apr 6, 2026
Merged

CI: Upgrade important CI environment#64744
potiuk merged 7 commits intoapache:mainfrom
astronomer:ci-upgrade-b91394aa4c

Conversation

@Lee-W
Copy link
Copy Markdown
Member

@Lee-W Lee-W commented Apr 5, 2026


Was generative AI tooling used to co-author this PR?
  • Yes (please specify the tool below)

Generated-by: Claude following the guidelines


  • Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
  • For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
  • When adding dependency, check compliance with the ASF 3rd Party License Policy.
  • For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

@Lee-W Lee-W force-pushed the ci-upgrade-b91394aa4c branch from d0da13f to d9dc22f Compare April 6, 2026 08:43
@Lee-W Lee-W force-pushed the ci-upgrade-b91394aa4c branch from ec4485f to 39a2084 Compare April 6, 2026 11:10
@Lee-W Lee-W requested a review from uranusjr as a code owner April 6, 2026 11:10
@Lee-W Lee-W force-pushed the ci-upgrade-b91394aa4c branch from 5b68018 to c3925e2 Compare April 6, 2026 11:53
@Lee-W Lee-W force-pushed the ci-upgrade-b91394aa4c branch from c3925e2 to d95ed63 Compare April 6, 2026 13:28
@potiuk potiuk merged commit 8401000 into apache:main Apr 6, 2026
148 checks passed
@potiuk
Copy link
Copy Markdown
Member

potiuk commented Apr 6, 2026

Nice! Thantks @Lee-W for persistency :)

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 6, 2026

Backport failed to create: v3-2-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.

Status Branch Result
v3-2-test Commit Link

You can attempt to backport this manually by running:

cherry_picker 8401000 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:

cherry_picker --continue

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

jscheffl pushed a commit to jscheffl/airflow that referenced this pull request Apr 6, 2026
* CI: Upgrade important CI environment

* style: fix provider mypy error

* fixup! style: fix provider mypy error

* fixup! fixup! style: fix provider mypy error

* fixup! fixup! fixup! style: fix provider mypy error

* fixup! fixup! fixup! style: fix provider mypy error

* fixup! fixup! fixup! style: fix provider mypy error

(cherry picked from commit 8401000)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:dev-tools backport-to-v3-2-test Mark PR with this label to backport to v3-2-test branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants