Skip to content

CI hardening: reject superseded rolling publishers - #6

Draft
mark-e-deyoung wants to merge 1 commit into
hardening/push-only-experimental-publisherfrom
hardening/serialize-experimental-publisher
Draft

CI hardening: reject superseded rolling publishers#6
mark-e-deyoung wants to merge 1 commit into
hardening/push-only-experimental-publisherfrom
hardening/serialize-experimental-publisher

Conversation

@mark-e-deyoung

Copy link
Copy Markdown

Purpose

Prevent an older in-flight push from overwriting a newer semper-exp-current candidate after publication authority is narrowed to branch pushes.

Implements #3 as a separate stacked change on top of #5.

Change

  • serialize the write-capable publish-experimental job with a dedicated concurrency group and cancellation of superseded publisher jobs;
  • immediately before tag/release mutation, resolve the current semper/compile-observer branch head and fail closed unless it still equals this workflow's candidate SHA.

Why both controls

Concurrency reduces overlapping write-capable publishers, but cancellation is cooperative. The branch-head check prevents a slower older build from publishing after a newer branch head already exists even if that older workflow reaches the publisher later.

Stack / rollout

This PR targets hardening/push-only-experimental-publisher so its diff remains independent from #5. Neither branch is the release-triggering semper/compile-observer branch.

Do not retarget/merge into the release branch until #5 and the private promotion state are ready.

Closes #3 when the stacked change ultimately lands on semper/compile-observer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant