fix(ci): gracefully fall back to GITHUB_TOKEN when App secrets absent#28
Merged
Merged
Conversation
Two issues when RELEASE_PLEASE_APP_ID/RELEASE_PLEASE_APP_PRIVATE_KEY are not configured: 1. create-github-app-token fails hard, skipping the release step. Add continue-on-error: true and fall back to secrets.GITHUB_TOKEN so release-please always runs. 2. fromJson(steps.release.outputs.pr).number in env: is evaluated before the if: guard, crashing with "Error reading JToken" when the release step was skipped (empty output). Move the extraction into the run: shell via jq, and tighten the if: to also require steps.app-token.outcome == 'success' so auto-merge only fires when the App token is actually available.
This was referenced Jun 6, 2026
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.
Two issues when RELEASE_PLEASE_APP_ID/RELEASE_PLEASE_APP_PRIVATE_KEY are not configured:
create-github-app-token fails hard, skipping the release step. Add continue-on-error: true and fall back to secrets.GITHUB_TOKEN so release-please always runs.
fromJson(steps.release.outputs.pr).number in env: is evaluated before the if: guard, crashing with "Error reading JToken" when the release step was skipped (empty output). Move the extraction into the run: shell via jq, and tighten the if: to also require steps.app-token.outcome == 'success' so auto-merge only fires when the App token is actually available.
Summary