Repository navigation
Use Clerk for scoped publishing keys - #18
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.
The public CLI can use GDAM’s new Clerk publishing keys through GDAM_API_KEY, retaining GDAM_SECRET_KEY for existing users. Clerk credentials are sent as Bearer tokens.
Publishing also now reads the registered repository and complete GitHub release/asset/commit facts before posting, matching the current index API contract. Previously the CLI sent only tag and asset names, which the current backend rejects. GitHub credentials remain on the publisher’s machine. The README recommends GitHub Actions OIDC for CI and scoped Clerk keys for manual publishing.
Validation: unit tests pass, including complete publish payload/authentication and published/draft/ambiguous/missing-digest GitHub fixtures. The complete pinned
make checkpassed, including all six release archives, artifact smoke checks, lint and race tests. Exact-head GitHub CI passed for37eaadd35c321e616d12cdda3cc4ff0962231c10.