Skip to content

fix: update dependencies to fix dependabot alarms in core#66629

Merged
potiuk merged 1 commit intoapache:mainfrom
jscheffl:bugfix/fix-dependabot-alarms-core-2026-05-09
May 10, 2026
Merged

fix: update dependencies to fix dependabot alarms in core#66629
potiuk merged 1 commit intoapache:mainfrom
jscheffl:bugfix/fix-dependabot-alarms-core-2026-05-09

Conversation

@jscheffl
Copy link
Copy Markdown
Contributor

@jscheffl jscheffl commented May 9, 2026


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

  • 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.

@jscheffl jscheffl force-pushed the bugfix/fix-dependabot-alarms-core-2026-05-09 branch from 8a54aa6 to e962cd5 Compare May 9, 2026 17:45
@jscheffl jscheffl changed the title Bugfix/fix dependabot alarms core 2026-05-09 fix: update dependencies to fix dependabot alarms in core May 9, 2026
@potiuk potiuk merged commit 45d2413 into apache:main May 10, 2026
82 checks passed
@github-actions
Copy link
Copy Markdown
Contributor

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 45d2413 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.

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

Labels

area:dev-tools area:providers area:UI Related to UI/UX. For Frontend Developers. backport-to-v3-2-test Mark PR with this label to backport to v3-2-test branch provider:common-ai

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants