Skip to content

Run one release image publish at a time #2623

Open

Description

@kmcginnes

Each release run of build_docker.yml gets a concurrency group of its own, so a merge to main can't cancel it (#2537). Two release runs started at the same moment can therefore both pass the publish checks from #2584 before either one pushes. Put every release run in one fixed group with cancel-in-progress: false, so release runs wait for each other while snapshot builds keep replacing each other. Check how a third queued release run behaves, since GitHub keeps one pending run per group, and say in the PR what happens to it. Do this after 3.3.3 ships, on main and 3.3.x.


Important

Internal only — this issue is maintained by the core team and is not accepting external contributions.


🤖 Written by an AI agent on my behalf.

Activity

  1. added
    infrastructureIssues related to tooling or deployment
    internalSignals that the team will work on this issue internally.
    github_actionsPull requests that update GitHub Actions code
    on Nov 17, 2026
  2. added theissue type on Nov 17, 2026
  3. added this to the Release v3.4 milestone on Nov 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    github_actionsPull requests that update GitHub Actions codeinfrastructureIssues related to tooling or deploymentinternalSignals that the team will work on this issue internally.

    Type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions