Skip to content

[main] Upgrade important CI environment - #72016

Merged
potiuk merged 1 commit into
mainfrom
ci-upgrade-main
Aug 25, 2026
Merged

[main] Upgrade important CI environment#72016
potiuk 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.

@Lee-W
Lee-W marked this pull request as ready for review August 24, 2026 08:02
@github-actions

Copy link
Copy Markdown
Contributor Author

uv.lock on main just moved via #52330 ("Add Apache Arrow provider"), commit 518fed3 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.

Rebased onto main. The autoupdate hunk that moved the lychee prek hook from
`lychee-lib-v0.24.2` to `# frozen: nightly` was dropped: `nightly` is a moving
tag lycheeverse re-points on every push to main, and v0.24.2 is still the newest
actual release, so that was a stable-release-to-nightly-snapshot swap rather
than a version bump.
@potiuk
potiuk merged commit b5ab83f into main Aug 25, 2026
64 checks passed
@potiuk
potiuk deleted the ci-upgrade-main branch August 25, 2026 15:03
@github-actions

Copy link
Copy Markdown
Contributor Author

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.

Status Branch Result
v3-3-test Commit Link

You can attempt to backport this manually by running:

cherry_picker b5ab83f 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 free to 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.

3 participants