fix: read APP_ID from org secrets instead of repo vars - #441
Merged
Conversation
The Generate GitHub App token step failed with '[@octokit/auth-app] appId option is required' because it referenced vars.APP_ID, but APP_ID was created as an organisation secret two months ago, not a repository variable. Point app-id at secrets.APP_ID. Also gate the token-generation and debug steps on new_release_published so docs-site config issues cannot fail a publish run that produced no release, and add a temporary debug step printing input lengths (never values) to confirm secret visibility.
allanbowe
approved these changes
Aug 24, 2026
|
🎉 This PR is included in version 5.2.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Problem
The last two publish runs on main failed at the docs-site steps:
CORESASJSIO_PAT(fixed in fix: replace expired PAT with GitHub App token for docs site publish #440)[@octokit/auth-app] appId option is requiredRoot cause
The workflow referenced
vars.APP_ID(a repository/org variable), but APP_ID was created as an organisation secret ~2 months ago.vars.APP_IDtherefore resolved to an empty string and the action aborted before reading the private key.Fix
app-idatsecrets.APP_IDnew_release_published == 'true'so docs-site config problems cannot fail publish runs that produce no releaseNote: the npm release itself is unaffected — v5.2.0 published successfully; only the docs-site publish chain was broken.