Migrate release tag/release creation to dd-octo-sts - #29
Merged
Conversation
An org-wide GitHub tag-protection ruleset blocks github-actions[bot] from creating tag/ref objects, which will break this workflow's gh release create step the same way it broke the SDK's release (v0.14.7). dd-octo-sts issues a short-lived, narrowly-scoped installation token via OIDC that is exempt from this restriction, per Datadog's sanctioned migration path. Adds a trust policy scoped to push events on main for this workflow only, and switches the release step to use the exchanged token instead of the default GITHUB_TOKEN. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
dbish
self-requested a review
July 14, 2026 15:14
dbish
approved these changes
Jul 14, 2026
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
2 participants
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
github-actions[bot]from creating tag/ref objects. The SDK repo (dispatch_agents_sdk) hit this on releasev0.14.7(GH013: Cannot create ref due to creations being restricted) and fixed it by migrating todd-octo-sts(datadog-labs/dispatch_agents_sdk#34).releasejob creates releases viagh release create ... --target $GITHUB_SHAusing the defaultGITHUB_TOKEN, which is subject to the same ruleset. It hasn't failed yet only because the last release predates the ruleset's rollout — this proactively ports the fix..github/chainguard/self.release.push.sts.yaml, a trust policy scoped topushevents onmainfor this exact workflow, grantingcontents: write.id-token: writepermission, add-octo-ststoken exchange step, and agh auth statusverification step, then switches the release step to use the exchanged token instead ofgithub.token.git tag/git push/actions/checkoutstep, so the follow-uppersist-credentials: falsefix from SDK PR #35 doesn't apply here.Test plan
python3 -c "import yaml; yaml.safe_load(open('.github/workflows/release.yml'))"and same for the new trust policy)Get dd-octo-sts token/Verify dd-octo-sts token/Create or update GitHub Releasesteps🤖 Generated with Claude Code