Skip to content

fix: use dd-octo-sts for release workflow authentication#83

Merged
rochdev merged 1 commit into
mainfrom
rochdev/fix-release-workflow-dd-octo-sts
Jun 9, 2026
Merged

fix: use dd-octo-sts for release workflow authentication#83
rochdev merged 1 commit into
mainfrom
rochdev/fix-release-workflow-dd-octo-sts

Conversation

@rochdev

@rochdev rochdev commented Jun 4, 2026

Copy link
Copy Markdown
Member

Summary

  • The release workflow for v0.1.12 failed with HTTP 403 because GITHUB_TOKEN write access is disabled org-wide
  • Switched both create-release and upload-assets jobs to use dd-octo-sts-action to obtain a scoped token
  • Added .github/chainguard/self.release.create-release.sts.yaml policy granting contents: write only to tag push events on this workflow

Test plan

  • Re-tag v0.1.12 (or a new tag) and verify the release workflow completes successfully

🤖 Generated with Claude Code

GITHUB_TOKEN write access is disabled org-wide; switch to dd-octo-sts
to obtain a scoped token with contents:write for tag push events.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@rochdev
rochdev marked this pull request as ready for review June 4, 2026 21:25
@rochdev
rochdev merged commit 2de7cb2 into main Jun 9, 2026
5 checks passed
@rochdev
rochdev deleted the rochdev/fix-release-workflow-dd-octo-sts branch June 9, 2026 11:27
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.

2 participants