You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Activity