Repository navigation
fix: use Clerk API key for first-party publishing - #19
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
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.
First-party publishing still referenced
TERMCADE_TOKENand a pre-Clerk CLI. Use the selected organizationTERMCADE_API_KEY, with CLI v0.0.13 and Bearer authentication in catalog recovery.Recovery now performs an authenticated publishing retry even when the catalog already exists, so a green run verifies the credential. Update its reviewed Asteroid coordinates to the existing v0.0.3 release while preserving exact package digest checks and the release provenance controls.
Validation: full pinned
make installandmake checkpassed, including every game's tests/WASM package validation and three offline recovery checks. Separate operator checks verified the replacement Clerk key against all three existing production releases (409 already published); no new release was created. Run the recovery workflow after merge before deleting the obsolete repository secret.Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.