Publish one exact Assistant release
Validate the current source, authorize that immutable release, and wait until its signed artifact is installable.
Make identity and behavior final
- Replace the starter
@your-github-usernamewith your verified Creator handle. - Choose a deliberate, unreleased semantic version in
shimpz.toml. - Test representative Actions and make the manifest, icon, network, and Integration declarations final.
- Run the command from the Assistant project whose exact source you intend to publish.
Every release is public after review
Every publication is public. A release appears in the Store only after a separate review approves it. Review controls discovery, not Team authority: the Team verifies and authorizes the exact artifact before installation.
Validate, authorize, and publish
shimpz assistant check Assistant is valid. shimpz assistant publish shimpz assistant publish builds the canonical source package, validates its generated contract, obtains identity:read and assistant:publish authorization when needed, records your exact Creator
consent, submits the release, and waits for its artifact. A separate shimpz auth step is not required.
Wait for one terminal state
The CLI polls every five seconds, honors server retry timing, and prints a state only when it changes. Normal progress is:
queued— The accepted release is waiting to start.resolving— Dependencies are being resolved and locked.building— The immutable amd64/arm64 image is being built.scanning— The image is being scanned and its SBOM generated.signing— The image and provenance are being signed.artifact_ready— The signed artifact is installable.
A failed build ends at build_failed with a safe reason and, when available, its build-run link.
Do not restart a publication while these states are advancing.
Confirm the artifact, not only the upload
Publication is complete only when the CLI prints:
Assistant published and installable.
The result includes source and OCI digests, review state, build run, signature, provenance, and the Developers
portal URL. The release appears in the Store only after its review state becomes approved.
Recover without changing the release accidentally
creator_consent_required- One or more attributed Creators have not consented to this exact id, version, and source digest.
version_already_published- Do not mutate that release. Choose a new version for changed source.
- Validation fails before upload
- Fix the first reported project field or file, rerun
shimpz assistant check, then publish again. - Dependency, test, scan, build, or signing failure
- Use the safe failure code and build-run URL. Fix authored source only when the failure belongs to it.
translation_failed- A message could not be translated within its field. Shorten or simplify the
shimpz.textcopy, then publish again. This code requires SDK 0.5.2 and CLI 0.5.64 or newer. - The wait reaches 30 minutes
- The CLI instructs you to rerun the same
shimpz assistant publishcommand with unchanged source.