Document trusted publishing setup, including immutable subject claims - #73
Open
nealrichardson wants to merge 1 commit into
Open
Document trusted publishing setup, including immutable subject claims#73nealrichardson wants to merge 1 commit into
nealrichardson wants to merge 1 commit into
Conversation
Adds a "Trusted publishing" section to the README covering how to authorize a repository on Connect, how to determine the `repository` subject-claim value (name-only vs. the immutable `owner@id/repo@id` form), and how to configure a trusted publisher from the command line with `posit connect api`. Extends the setup-connect-deploy skill with a new Step 3a that offers to authorize the repository on Connect when the user chooses trusted publishing, reading the subject-claim format from GitHub rather than guessing it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
|
Preview deployed to Connect ( Deployed from commit be439e9. |
Contributor
|
Cleaned up 1 preview bundle(s) on http://localhost:3942: 8 |
Contributor
|
Preview deployed to Connect ( Deployed from commit be439e9. |
Contributor
|
Cleaned up 1 preview bundle(s) on http://localhost:3941: 8 |
Contributor
|
Preview deployed to Connect ( Deployed from commit be439e9. |
Contributor
|
Cleaned up 1 preview bundle(s) on http://localhost:3940: 8 |
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.
Fixes #72.
GitHub repos created on or after 2026-07-15 issue OIDC tokens with immutable subject claims (
my-org@123456/my-repo@789012instead ofmy-org/my-repo). Connect accepts either form in a trusted publisher's Repository field, but it has to match what the repo actually produces — get it wrong and the token exchange fails with an HTTP 400 while the configuration looks correct. Nothing in this repo said so.README
New Trusted publishing section, linked from the prerequisites list, the feature-support table, and the
deployauth docs:gh api repos/$ORG/$REPO/actions/oidc/customization/sub(reports what the repo actually produces, needs admin); the fallback builds the immutable form from owner/repo IDs, as in the issue.posit connect loginas a human (a trusted-publishing credential can't manage trusted publishers), thenPOST v1/content/$GUID/trusted-publishersviaposit connect api, plus list/revoke.setup-connect-deployskillNew Step 3a, reached only when the user chooses trusted publishing, that offers to authorize the repository on Connect:
repositoryby asking GitHub for the subject claim prefix, with the ID-based fallback when the endpoint 403s. If the prefix isn'trepo:-shaped (customized claim template), it stops and points at a Custom OpenID Connect publisher instead of registering something that can't match.posit connect loginthemselves.Error handling maps 402/403/404 to license, permissions, and server-too-old respectively, recommending API-key auth in each case. Step 6's summary now reports the registered
repositoryvalue so a later repo rename is a known breaking change.Docs only — no action or package code changed.
🤖 Generated with Claude Code