Skip to content

fix(docker-release): export GH_TOKEN so stevedore can cut the GitHub Release #64

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
blairham merged 1 commit into from
Aug 22, 2026
Merged

fix(docker-release): export GH_TOKEN so stevedore can cut the GitHub Release #64

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions .github/workflows/docker-release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -203,6 +203,16 @@ jobs:
# entries simply ignore these.
STEVEDORE_CACHE_FROM: "type=gha,scope=stevedore"
STEVEDORE_CACHE_TO: "type=gha,mode=max,scope=stevedore"
# stevedore's release step shells out to `gh release create`, which
# authenticates from GH_TOKEN and takes no token flag. Without it the
# image publishes and the job THEN dies on `gh: exit status 4`, so a
# red run sits behind a completed push and the tag gets no GitHub
# Release (pinpredict/.github#63, understudy#225). The job's
# `contents: write` above is what lets this token create the release.
# Not to be confused with GH_PRIVATE_TOKEN below: that one is a minted
# App token with contents:read, for fetching private modules inside
# the BUILD, and it cannot create a release.
GH_TOKEN: ${{ github.token }}
# Empty unless private-modules minted a token above. The repo's
# .stevedore.yaml declares `secrets: [{id: gh_token, env:
# GH_PRIVATE_TOKEN}]`; when private-modules is true this is populated,
Expand Down