Replace the Cancel workflow with native GitHub Action functionality. - #32016

…32016)

* Replace the Cancel workflow with native GitHub Action functionality.

Recently, GitHub introduced the `concurrency` option for ensuring that only a single job or workflow using the same concurrency group will run at a time.

Currently, there is a Cancel workflow in the repo that aims to accomplish the same thing. However, when a backlog exists, the Cancel workflow for each commit does not run until its turn in the queue is reached. This can result in the backlog ballooning.

The `concurrency` option in GitHub Actions runs a check when a workflow is queued, skipping the need to wait for an available runner to cancel old workflows.

(cherry picked from commit 7b39dd7)

Ports upstream trunk commit 7b39dd7
(WordPress@7b39dd7),
"Replace the Cancel workflow with native GitHub Action functionality (WordPress#32016)":
adds a `concurrency:` block to every relevant workflow so in-progress runs are
cancelled automatically when a newer commit supersedes them, and removes the
now-redundant `cancel.yml` workflow if still present on this branch.

Workflows that didn't exist (or looked different) back when the upstream commit
landed were brought in line with how trunk configures concurrency for them today.

This branch has no `cancel.yml` workflow to remove and no
`enforce-pr-labels.yml`/`pull-request-automation.yml`/reusable-workflow-only
files to skip. All five workflow files present on this branch
(`bundle-size.yml`, `create-block.yml`, `end2end-test.yml`, `static-checks.yml`,
`unit-test.yml`) trigger on plain `pull_request:` and got the standard
concurrency block.

Ports upstream trunk commit 7b39dd7
(WordPress@7b39dd7),
"Replace the Cancel workflow with native GitHub Action functionality (WordPress#32016)":
adds a `concurrency:` block to every relevant workflow so in-progress runs are
cancelled automatically when a newer commit supersedes them, and removes the
now-redundant `cancel.yml` workflow if still present on this branch.

Workflows that didn't exist (or looked different) back when the upstream commit
landed were brought in line with how trunk configures concurrency for them today.

Ports upstream trunk commit 7b39dd7
(WordPress@7b39dd7),
"Replace the Cancel workflow with native GitHub Action functionality (WordPress#32016)":
adds a `concurrency:` block to every relevant workflow so in-progress runs are
cancelled automatically when a newer commit supersedes them, and removes the
now-redundant `cancel.yml` workflow if still present on this branch.

Workflows that didn't exist (or looked different) back when the upstream commit
landed were brought in line with how trunk configures concurrency for them today.

Ports upstream trunk commit 7b39dd7
(WordPress@7b39dd7),
"Replace the Cancel workflow with native GitHub Action functionality (WordPress#32016)":
adds a `concurrency:` block to every relevant workflow so in-progress runs are
cancelled automatically when a newer commit supersedes them, and removes the
now-redundant `cancel.yml` workflow if still present on this branch.

Workflows that didn't exist (or looked different) back when the upstream commit
landed were brought in line with how trunk configures concurrency for them today.

This branch has no `cancel.yml` workflow to remove and no
`enforce-pr-labels.yml`/`pull-request-automation.yml`/reusable-workflow-only
files to skip. All five workflow files present on this branch
(`bundle-size.yml`, `create-block.yml`, `end2end-test.yml`, `static-checks.yml`,
`unit-test.yml`) trigger on plain `pull_request:` and got the standard
concurrency block.

Ports upstream trunk commit 7b39dd7
(WordPress@7b39dd7),
"Replace the Cancel workflow with native GitHub Action functionality (WordPress#32016)":
adds a `concurrency:` block to every relevant workflow so in-progress runs are
cancelled automatically when a newer commit supersedes them, and removes the
now-redundant `cancel.yml` workflow if still present on this branch.

Workflows that didn't exist (or looked different) back when the upstream commit
landed were brought in line with how trunk configures concurrency for them today.

Ports upstream trunk commit 7b39dd7
(WordPress@7b39dd7),
"Replace the Cancel workflow with native GitHub Action functionality (WordPress#32016)":
adds a `concurrency:` block to every relevant workflow so in-progress runs are
cancelled automatically when a newer commit supersedes them, and removes the
now-redundant `cancel.yml` workflow if still present on this branch.

Workflows that didn't exist (or looked different) back when the upstream commit
landed were brought in line with how trunk configures concurrency for them today.

On this branch, `cancel.yml` no longer exists (already removed earlier in this
project's repair stack), and every workflow file already had a `concurrency:`
block except `check-components-changelog.yml` and `php-changes-detection.yml`,
which this commit brings in line with the rest.

Ports upstream trunk commit 7b39dd7
(WordPress@7b39dd7),
"Replace the Cancel workflow with native GitHub Action functionality (WordPress#32016)":
adds a `concurrency:` block to every relevant workflow so in-progress runs are
cancelled automatically when a newer commit supersedes them, and removes the
now-redundant `cancel.yml` workflow if still present on this branch.

Workflows that didn't exist (or looked different) back when the upstream commit
landed were brought in line with how trunk configures concurrency for them today.

`wp/6.6` was cut well after the upstream commit landed, so nearly every workflow
file already carried the standard `concurrency:` block natively. The only
exception was `php-changes-detection.yml`, which never had one. `cancel.yml`
does not exist on this branch, so there was nothing to remove.

Ports upstream trunk commit 7b39dd7
(WordPress@7b39dd7),
"Replace the Cancel workflow with native GitHub Action functionality (WordPress#32016)":
adds a `concurrency:` block to every relevant workflow so in-progress runs are
cancelled automatically when a newer commit supersedes them, and removes the
now-redundant `cancel.yml` workflow if still present on this branch.

Workflows that didn't exist (or looked different) back when the upstream commit
landed were brought in line with how trunk configures concurrency for them today.

`wp/6.6` was cut well after the upstream commit landed, so nearly every workflow
file already carried the standard `concurrency:` block natively. The only
exception was `php-changes-detection.yml`, which never had one. `cancel.yml`
does not exist on this branch, so there was nothing to remove.

Ports upstream trunk commit 7b39dd7
(WordPress@7b39dd7),
"Replace the Cancel workflow with native GitHub Action functionality (WordPress#32016)":
adds a `concurrency:` block to every relevant workflow so in-progress runs are
cancelled automatically when a newer commit supersedes them, and removes the
now-redundant `cancel.yml` workflow if still present on this branch.

Workflows that didn't exist (or looked different) back when the upstream commit
landed were brought in line with how trunk configures concurrency for them today.

`wp/6.6` was cut well after the upstream commit landed, so nearly every workflow
file already carried the standard `concurrency:` block natively. The only
exception was `php-changes-detection.yml`, which never had one. `cancel.yml`
does not exist on this branch, so there was nothing to remove.

Ports upstream trunk commit 7b39dd7
(WordPress@7b39dd7),
"Replace the Cancel workflow with native GitHub Action functionality (WordPress#32016)":
adds a `concurrency:` block to every relevant workflow so in-progress runs are
cancelled automatically when a newer commit supersedes them, and removes the
now-redundant `cancel.yml` workflow if still present on this branch.

Workflows that didn't exist (or looked different) back when the upstream commit
landed were brought in line with how trunk configures concurrency for them today.

Ports upstream trunk commit 7b39dd7
(WordPress@7b39dd7),
"Replace the Cancel workflow with native GitHub Action functionality (WordPress#32016)":
adds a `concurrency:` block to every relevant workflow so in-progress runs are
cancelled automatically when a newer commit supersedes them, and removes the
now-redundant `cancel.yml` workflow if still present on this branch.

Workflows that didn't exist (or looked different) back when the upstream commit
landed were brought in line with how trunk configures concurrency for them today.

Ports upstream trunk commit 7b39dd7
(WordPress@7b39dd7),
"Replace the Cancel workflow with native GitHub Action functionality (WordPress#32016)":
adds a `concurrency:` block to every relevant workflow so in-progress runs are
cancelled automatically when a newer commit supersedes them, and removes the
now-redundant `cancel.yml` workflow if still present on this branch.

Workflows that didn't exist (or looked different) back when the upstream commit
landed were brought in line with how trunk configures concurrency for them today.

On this branch, `cancel.yml` no longer exists (already removed earlier in this
project's repair stack), and every workflow file already had a `concurrency:`
block except `check-components-changelog.yml` and `php-changes-detection.yml`,
which this commit brings in line with the rest.

Ports upstream trunk commit 7b39dd7
(WordPress@7b39dd7),
"Replace the Cancel workflow with native GitHub Action functionality (WordPress#32016)":
adds a `concurrency:` block to every relevant workflow so in-progress runs are
cancelled automatically when a newer commit supersedes them, and removes the
now-redundant `cancel.yml` workflow if still present on this branch.

Workflows that didn't exist (or looked different) back when the upstream commit
landed were brought in line with how trunk configures concurrency for them today.

On this branch, every workflow file except `flaky-tests.yml` already carried the
standard concurrency block from the branch's own original content. `cancel.yml`
does not exist on this branch, so there was nothing to remove. `flaky-tests.yml`
(triggered only by `workflow_run`) gets the standard block added here, matching
how trunk configures concurrency for workflows with no `pull_request` trigger.

Ports upstream trunk commit 7b39dd7
(WordPress@7b39dd7),
"Replace the Cancel workflow with native GitHub Action functionality (WordPress#32016)":
adds a `concurrency:` block to every relevant workflow so in-progress runs are
cancelled automatically when a newer commit supersedes them, and removes the
now-redundant `cancel.yml` workflow if still present on this branch.

Workflows that didn't exist (or looked different) back when the upstream commit
landed were brought in line with how trunk configures concurrency for them today.

Ports upstream trunk commit 7b39dd7
(WordPress@7b39dd7),
"Replace the Cancel workflow with native GitHub Action functionality (WordPress#32016)":
adds a `concurrency:` block to every relevant workflow so in-progress runs are
cancelled automatically when a newer commit supersedes them, and removes the
now-redundant `cancel.yml` workflow if still present on this branch.

Workflows that didn't exist (or looked different) back when the upstream commit
landed were brought in line with how trunk configures concurrency for them today.

This branch has no `cancel.yml` workflow to remove and no
`enforce-pr-labels.yml`/`pull-request-automation.yml`/reusable-workflow-only
files to skip. All five workflow files present on this branch
(`bundle-size.yml`, `create-block.yml`, `end2end-test.yml`, `static-checks.yml`,
`unit-test.yml`) trigger on plain `pull_request:` and got the standard
concurrency block.

`cancel.yml` runs a single `Cancel Previous Runs` job on
`pull_request`: it curls the GitHub API for every workflow ID in the
repository and passes the list to `styfle/cancel-workflow-action`,
which cancels any still-running earlier runs for the same pull
request. GitHub Actions has since gained a native `concurrency:` key
with `cancel-in-progress: true` that does exactly this, without an
API round trip or a third-party action holding `GITHUB_TOKEN`.
Upstream trunk replaced the workflow for that reason in
`7b39dd71905cb7e546857741e3d52e977ec36691`, "Replace the Cancel
workflow with native GitHub Action functionality (WordPress#32016)"; a later
commit in this series adds the equivalent `concurrency:` blocks to
this branch's workflows.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DtSAAJkQ9P6vPtDumqStg8

Ports upstream trunk commit 7b39dd7
(WordPress@7b39dd7),
"Replace the Cancel workflow with native GitHub Action functionality (WordPress#32016)":
adds a `concurrency:` block to every relevant workflow so in-progress runs are
cancelled automatically when a newer commit supersedes them. The `cancel.yml`
workflow this replaces is removed earlier in this series, alongside the branch's
other obsolete workflows.

Workflows that didn't exist (or looked different) back when the upstream commit
landed were brought in line with how trunk configures concurrency for them today.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DtSAAJkQ9P6vPtDumqStg8

`cancel.yml` ran on every `pull_request` event, curled the repository's full
workflow list out of the REST API to build a `WORKFLOW_IDS_TO_CANCEL` list, and
handed it to `styfle/cancel-workflow-action` so that a pull request's older
in-progress runs were cancelled when a newer push superseded them. It exists
only because GitHub Actions had no built-in way to do that when this branch was
cut. It has since grown one: a workflow-level `concurrency:` block with
`cancel-in-progress: true`, which cancels superseded runs directly, without
spending a runner, an API call, or a `GITHUB_TOKEN` on a third-party action to
do it. Upstream replaced this workflow with that native configuration in
`7b39dd71905cb7e546857741e3d52e977ec36691`, "Replace the Cancel workflow with
native GitHub Action functionality (WordPress#32016)", and a later change in this series
ports the same `concurrency:` blocks to this branch.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DtSAAJkQ9P6vPtDumqStg8

Ports upstream trunk commit 7b39dd7
(WordPress@7b39dd7),
"Replace the Cancel workflow with native GitHub Action functionality (WordPress#32016)":
adds a `concurrency:` block to every relevant workflow so in-progress runs are
cancelled automatically when a newer commit supersedes them. The `cancel.yml`
workflow this configuration supersedes is removed earlier in this series, with
the branch's other obsolete workflows.

Workflows that didn't exist (or looked different) back when the upstream commit
landed were brought in line with how trunk configures concurrency for them today.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DtSAAJkQ9P6vPtDumqStg8

`cancel.yml` runs a single `Cancel Previous Runs` job on
`pull_request`: it curls the GitHub API for every workflow ID in the
repository and passes the list to `styfle/cancel-workflow-action`,
which cancels any still-running earlier runs for the same pull
request. GitHub Actions has since gained a native `concurrency:` key
with `cancel-in-progress: true` that does exactly this, without an
API round trip or a third-party action holding `GITHUB_TOKEN`.
Upstream trunk replaced the workflow for that reason in
`7b39dd71905cb7e546857741e3d52e977ec36691`, "Replace the Cancel
workflow with native GitHub Action functionality (WordPress#32016)"; a later
commit in this series adds the equivalent `concurrency:` blocks to
this branch's workflows.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DtSAAJkQ9P6vPtDumqStg8

Ports upstream trunk commit 7b39dd7
(WordPress@7b39dd7),
"Replace the Cancel workflow with native GitHub Action functionality (WordPress#32016)":
adds a `concurrency:` block to every relevant workflow so in-progress runs are
cancelled automatically when a newer commit supersedes them. The `cancel.yml`
workflow this replaces is removed earlier in this series, alongside the branch's
other obsolete workflows.

Workflows that didn't exist (or looked different) back when the upstream commit
landed were brought in line with how trunk configures concurrency for them today.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DtSAAJkQ9P6vPtDumqStg8

`cancel.yml` runs a single `Cancel Previous Runs` job on
`pull_request`: it curls the GitHub API for every workflow ID in the
repository and passes the list to `styfle/cancel-workflow-action`,
which cancels any still-running earlier runs for the same pull
request. GitHub Actions has since gained a native `concurrency:` key
with `cancel-in-progress: true` that does exactly this, without an
API round trip or a third-party action holding `GITHUB_TOKEN`.
Upstream trunk replaced the workflow for that reason in
`7b39dd71905cb7e546857741e3d52e977ec36691`, "Replace the Cancel
workflow with native GitHub Action functionality (WordPress#32016)"; a later
commit in this series adds the equivalent `concurrency:` blocks to
this branch's workflows.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DtSAAJkQ9P6vPtDumqStg8

Ports upstream trunk commit 7b39dd7
(WordPress@7b39dd7),
"Replace the Cancel workflow with native GitHub Action functionality (WordPress#32016)":
adds a `concurrency:` block to every relevant workflow so in-progress runs are
cancelled automatically when a newer commit supersedes them. The `cancel.yml`
workflow this replaces is removed earlier in this series, alongside the branch's
other obsolete workflows.

Workflows that didn't exist (or looked different) back when the upstream commit
landed were brought in line with how trunk configures concurrency for them today.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DtSAAJkQ9P6vPtDumqStg8

`cancel.yml` ran on every `pull_request` event, curled the repository's full
workflow list out of the REST API to build a `WORKFLOW_IDS_TO_CANCEL` list, and
handed it to `styfle/cancel-workflow-action` so that a pull request's older
in-progress runs were cancelled when a newer push superseded them. It exists
only because GitHub Actions had no built-in way to do that when this branch was
cut. It has since grown one: a workflow-level `concurrency:` block with
`cancel-in-progress: true`, which cancels superseded runs directly, without
spending a runner, an API call, or a `GITHUB_TOKEN` on a third-party action to
do it. Upstream replaced this workflow with that native configuration in
`7b39dd71905cb7e546857741e3d52e977ec36691`, "Replace the Cancel workflow with
native GitHub Action functionality (WordPress#32016)", and a later change in this series
ports the same `concurrency:` blocks to this branch.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DtSAAJkQ9P6vPtDumqStg8

Ports upstream trunk commit 7b39dd7
(WordPress@7b39dd7),
"Replace the Cancel workflow with native GitHub Action functionality (WordPress#32016)":
adds a `concurrency:` block to every relevant workflow so in-progress runs are
cancelled automatically when a newer commit supersedes them. The `cancel.yml`
workflow this configuration supersedes is removed earlier in this series, with
the branch's other obsolete workflows.

Workflows that didn't exist (or looked different) back when the upstream commit
landed were brought in line with how trunk configures concurrency for them today.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DtSAAJkQ9P6vPtDumqStg8

Ports upstream trunk commit 7b39dd7
(WordPress@7b39dd7),
"Replace the Cancel workflow with native GitHub Action functionality (WordPress#32016)":
adds a `concurrency:` block to every relevant workflow so in-progress runs are
cancelled automatically when a newer commit supersedes them, and removes the
now-redundant `cancel.yml` workflow if still present on this branch.

Workflows that didn't exist (or looked different) back when the upstream commit
landed were brought in line with how trunk configures concurrency for them today.

This branch has no `cancel.yml` workflow to remove and no
`enforce-pr-labels.yml`/`pull-request-automation.yml`/reusable-workflow-only
files to skip. All five workflow files present on this branch
(`bundle-size.yml`, `create-block.yml`, `end2end-test.yml`, `static-checks.yml`,
`unit-test.yml`) trigger on plain `pull_request:` and got the standard
concurrency block.