Prepare credentials and signing identity
publisherctl is provided through the private publisher/contributor distribution channel. It writes new files only and requires the private seed file to be owner-readable. Challenge and assertion payload files must contain the exact supplied bytes, without an added newline.
- An owner creates a product-scoped automation credential with the narrowest release scopes needed by the pipeline. Keep its expiry visible in CI operations.
- Generate a publisher Ed25519 key in your signing environment. Register only the public key through the owner workflow and sign the exact server-provided possession challenge.
- Store the private seed separately from the automation token. Publisher signing identity, platform review approval and central TUF signing are distinct controls.
publisherctl keygen -key publisher-private.hex -public publisher-public.hex
publisherctl sign -key publisher-private.hex -payload challenge.txt -out challenge-signature.hexBuild pipeline sequence
- Read the product workspace and choose a valid release family and channel.
- Create a release draft with version, access class, compatibility baseline, permissions and release notes.
- Create an upload session, transfer to the returned destination using its scoped upload credentials, confirm any multipart pieces, then complete the upload.
- Request validation and poll the validation runs. Bind any publisher assertion to the exact current release revision and artifact digests.
- Read publication preflight. Publish only when the approved revision and digests still match. Scheduling is a browser owner/release-manager workflow with recent authentication.
- Wait for the release and publication workflow to complete. A successful publish command alone does not mean clients can see a new signed channel head.
Treat conflicts as new information
Expected revisions prevent a pipeline from overwriting a colleague’s newer changes. Do not blindly fetch a revision and retry a publish: review the new inputs and approvals. Keep immutable artifact names, hashes and version records with your build evidence.
Upload tokens authorize only the exact upload destination. They are separate from publisher bearer credentials and short-lived artifact download grants. Do not forward a publisher token to an object-storage host.