Automate post-tag wheel publishing handoff - #3077
Merged
Merged
Conversation
dkirov-dd
force-pushed
the
bits/autonomous-wheel-publishing-handoff
branch
from
July 29, 2026 13:21
6306c89 to
ffc01ee
Compare
steveny91
approved these changes
Jul 29, 2026
This was referenced Aug 4, 2026
Draft
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
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.
Summary
create-tags: falseactions: writedispatch policyRelease flow
merge M → legacy signing commit S → tags at S → legacy build trigger → GitHub workflow_dispatch(source-repo-ref=S)GitLab remains the sole tag writer. GitHub receives
contents: readonly and detects packages from existing tags atS.Verification
bash -nand ShellCheck for both release scriptsgit diff --checkDownstream compatibility
The existing central builder trust policy already permits
workflow_dispatchon integrations-extrasmasterthrough integrations-core's reusable workflow. Builder-to-TUF dispatch remains unchanged, and the TUFreleaseenvironment has no required reviewers. No central builder or TUF runtime file is modified.Related marketplace handoff: https://github.com/DataDog/marketplace/pull/1696
Investigation and design: https://github.com/DataDog/agent-integrations-tuf/pull/91
Dependencies and rollout
Manual recovery remains available through
workflow_dispatchwith the signed/tagged SHA and optional explicit package list.Rollback
Disable the post-tag dispatch call while retaining legacy signing/tagging. Revert the receiver trigger/policy changes only after ensuring no stale old workflow run can create tags.