Repository navigation
Use Clerk for scoped publishing keys - #35
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.
Accept Termcade’s Clerk-issued ak_ publishing credentials in TERMCADE_TOKEN and send them as Bearer tokens. Existing tck_ publishing keys remain supported. Publishing credentials remain distinct from browser-approved tcc_ login sessions.
Update public usage instructions and verify the Clerk publish request against an offline HTTP server. Validation: the complete pinned
make checkpassed (five-platform archives, lint, race tests and released-SDK consumer checks). GitHub CI passed for exact head595774e7ee7d1bfcb2e7e8ea125a4859d5afb4bf.