Skip to content

add concurrency in update-constrants-on-push#64645

Merged
potiuk merged 1 commit intoapache:mainfrom
henry3260:add-concurrency-in-update-constrants-on-push
Apr 3, 2026
Merged

add concurrency in update-constrants-on-push#64645
potiuk merged 1 commit intoapache:mainfrom
henry3260:add-concurrency-in-update-constrants-on-push

Conversation

@henry3260
Copy link
Copy Markdown
Contributor

add concurrency in update-constrants-on-push

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.

@boring-cyborg boring-cyborg bot added area:dev-tools backport-to-v3-2-test Mark PR with this label to backport to v3-2-test branch labels Apr 2, 2026
@henry3260 henry3260 marked this pull request as ready for review April 3, 2026 11:51
@potiuk
Copy link
Copy Markdown
Member

potiuk commented Apr 3, 2026

Good catch. Not very likely to happen (but it did for v3-2-test subsequent uv.lock updates.

@potiuk potiuk merged commit 7047e03 into apache:main Apr 3, 2026
258 of 259 checks passed
github-actions bot pushed a commit that referenced this pull request Apr 3, 2026
(cherry picked from commit 7047e03)

Co-authored-by: Henry Chen <henryhenry0512@gmail.com>
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 3, 2026

Backport successfully created: v3-2-test

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 PR Link

potiuk pushed a commit that referenced this pull request Apr 3, 2026
…4671)

(cherry picked from commit 7047e03)

Co-authored-by: Henry Chen <henryhenry0512@gmail.com>
vatsrahul1001 pushed a commit that referenced this pull request Apr 8, 2026
…4671)

(cherry picked from commit 7047e03)

Co-authored-by: Henry Chen <henryhenry0512@gmail.com>
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.

2 participants