Fix newsfragment check being cancelled on rapid PR events#64447
Merged
potiuk merged 1 commit intoapache:mainfrom Mar 30, 2026
Merged
Fix newsfragment check being cancelled on rapid PR events#64447potiuk merged 1 commit intoapache:mainfrom
potiuk merged 1 commit intoapache:mainfrom
Conversation
potiuk
requested review from
Fokko,
RNHTTR,
amoghrajesh,
ashb,
bolkedebruin,
bugraoz93,
choo121600,
dheerajturaga,
dstandish,
ephraimbuddy,
gopidesupavan,
hussein-awala,
jason810496,
jedcunningham,
josh-fell,
jscheffl,
kaxil,
mobuchowski,
o-nikolas,
shahar1 and
vincbeck
as code owners
boring-cyborg
bot
added
area:airflow-ctl
area:API
boring-cyborg
bot
added
backport-to-v3-2-test
Change cancel-in-progress from true to false so that concurrent runs queue instead of cancelling each other. This check is very lightweight (single API call) so queueing has no downside, and avoids spurious "Cancelled" status on PRs that receive multiple events in quick succession (e.g. push + label change).
potiuk
force-pushed
the
fix-newsfragment-check-cancellation
branch
from
c102e88 to
d5d5f5f
Compare
bugraoz93
approved these changes
Mar 30, 2026
github-actions bot
pushed a commit
that referenced
this pull request
Mar 30, 2026
…#64447) Change cancel-in-progress from true to false so that concurrent runs queue instead of cancelling each other. This check is very lightweight (single API call) so queueing has no downside, and avoids spurious "Cancelled" status on PRs that receive multiple events in quick succession (e.g. push + label change). (cherry picked from commit 7e29628) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
Backport successfully created: v3-2-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
potiuk
added a commit
that referenced
this pull request
Apr 1, 2026
…#64447) (#64495) Change cancel-in-progress from true to false so that concurrent runs queue instead of cancelling each other. This check is very lightweight (single API call) so queueing has no downside, and avoids spurious "Cancelled" status on PRs that receive multiple events in quick succession (e.g. push + label change). (cherry picked from commit 7e29628) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
Subham-KRLX
pushed a commit
to Subham-KRLX/airflow
that referenced
this pull request
Apr 3, 2026
Change cancel-in-progress from true to false so that concurrent runs queue instead of cancelling each other. This check is very lightweight (single API call) so queueing has no downside, and avoids spurious "Cancelled" status on PRs that receive multiple events in quick succession (e.g. push + label change).
Suraj-kumar00
pushed a commit
to Suraj-kumar00/airflow
that referenced
this pull request
Apr 7, 2026
Change cancel-in-progress from true to false so that concurrent runs queue instead of cancelling each other. This check is very lightweight (single API call) so queueing has no downside, and avoids spurious "Cancelled" status on PRs that receive multiple events in quick succession (e.g. push + label change).
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 8, 2026
…#64447) (#64495) Change cancel-in-progress from true to false so that concurrent runs queue instead of cancelling each other. This check is very lightweight (single API call) so queueing has no downside, and avoids spurious "Cancelled" status on PRs that receive multiple events in quick succession (e.g. push + label change). (cherry picked from commit 7e29628) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Change
cancel-in-progressfromtruetofalsein thecheck-newsfragment-pr-number workflow's concurrency group.
With
cancel-in-progress: true, when a PR receives multiple eventsin quick succession (e.g. a push followed by a label change, or
rapid consecutive pushes), the earlier run gets cancelled by the
newer one, leaving a spurious "Cancelled" status on the PR.
This check is extremely lightweight (a single
gh apicall thatruns in seconds), so queueing concurrent runs has no downside
and avoids the cancelled status issue.
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Claude Opus 4.6) following the guidelines