Repository navigation
Expose release API failures and document token permissions - #127
Merged
Merged
Conversation
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
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.
Release API failures currently collapse to
gh api failed, hiding both the endpoint and HTTP status. Identify the failed API method/path and safe HTTP status, with a token/tag-rule hint for denied reference creation. Keep response bodies, stderr and credentials out of diagnostics.Document Workflows write alongside Contents write for RELEASE_BOT_TOKEN, including classic PAT scope guidance. GitHub documents this additional permission set for reference creation: https://docs.github.com/en/rest/git/refs#create-a-reference.
Investigation of run 40118993094: same-version preparation succeeded. A read-only replay of finalization passed the real CI/base/tree checks and reached POST git/refs; it stopped before mutation. The existing log does not reveal the failed endpoint/status, so token permissions remain a hypothesis until verified. This PR fixes observability and setup documentation; it cannot change the stored PAT permissions.
Validation:
bundle exec fastlane android python_checkspassed (79 tests and pinned formatting checks);git diff --checkpassed. Regression coverage includes HTTP 403, 422, network errors, and suppression of synthetic secrets/GH_DEBUG. No tag or release publication was started.