Skip to content

Scope WinGet token to the submit step only#358

Open
AndreyVMarkelov wants to merge 1 commit into
masterfrom
feature/winget-token-step-scope
Open

Scope WinGet token to the submit step only#358
AndreyVMarkelov wants to merge 1 commit into
masterfrom
feature/winget-token-step-scope

Conversation

@AndreyVMarkelov

Copy link
Copy Markdown
Contributor

Summary

Follow-up to #357. Moves WINGET_CREATE_GITHUB_TOKEN from the winget job's env down to the Submit WinGet manifest step's env.

Why

The token is only needed when WingetCreate opens the pull request. With it declared at job level it was also present in the environment of the Download WingetCreate step, which fetches and checksums an executable over the network. Scoping the secret to the single step that needs it follows least-privilege and reduces its exposure surface.

Changes

  • .github/workflows/release.yml — token declared at step level instead of job level.

Verification

  • YAML validates.
  • The presence check (throw if the secret is unset) and the WingetCreate invocation both remain within the step that now owns the token, so behavior is unchanged.

🤖 Generated with Claude Code

Move WINGET_CREATE_GITHUB_TOKEN from the winget job's env down to the
Submit WinGet manifest step. The secret is only needed when WingetCreate
opens the pull request, so the Download WingetCreate step no longer has
the token in its environment while fetching and checksumming the tool.
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