Harden release prepare authentication#53
Merged
Conversation
Use the built-in GitHub token for the initial checkout, then configure Git to use the selected release prepare token for branch pushes and PR creation. This avoids failing checkout before the workflow can validate the configured token.
This was referenced May 15, 2026
Closed
Closed
Merged
JanJakes
added a commit
that referenced
this pull request
May 15, 2026
## Release `v0.1.14` Version bump and release metadata update for `v0.1.14`. **Changelog draft:** * Add remote-site cache branching ([#40](#40)) * Bootstrap Starlight documentation site ([#42](#42)) * Add COW mergeback and audit model * Polish branch merge UI and harden audit follow-ups * Guard COW row merges against target trigger rewrites * Rewrite README and restructure documentation ([#47](#47)) * Add Linux XFS loop storage fallback ([#41](#41)) * Harden merge reliability gates and semantic coverage ([#46](#46)) * Automate release preparation and publishing ([#50](#50)) * Harden release prepare authentication ([#53](#53)) * Fix release prepare status parsing ([#54](#54)) * Polish release pull request handling ([#56](#56)) * Clarify release workflow stages **Full changelog:** v0.1.13-windows-cow.3...release/v0.1.14 ## Next steps 1. **Review** the changes in this pull request. 2. **Push** any additional edits to this branch (`release/v0.1.14`). 3. **Merge** this pull request to publish `v0.1.14`. Merging will automatically build ForkPress binaries, create a GitHub release, and update the Homebrew formula. Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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
1 participant
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
RELEASE_PREPARE_TOKENbefore checkout so bad or pending tokens fail with a direct API-auth error.GITHUB_TOKENfor the initial checkout instead of the custom release token.gh auth setup-gitso the selected release token is still used for release branch pushes and PR creation.Testing
git diff --checknpm testgh auth setup-git+git ls-remotesmoke test with the currentghtoken