Publish a team to CliqHub
Packages the manifest you send (plus dockerfile, dependencies and roles
when given) and publishes it to CliqHub as the version in the manifest’s
top-level version: field. The local catalog is not read, so a team does not
have to be installed to be published.
Use dry_run: true to run every local check (scope, version, sign-in, target
CliqHub) without uploading; the reply then has published: false.
force is accepted but has no effect: CliqHub never overwrites a published
version (HUB_VERSION_ALREADY_EXISTS).
From the CLI: cliq team publish ./path/to/team --access private.
No credential is needed from this machine. From another host, send Authorization: Bearer with a dispatch token CliqHub signed for this daemon or a cliq_tok_… personal token of a user in the daemon’s realm; this only works once the daemon is connected to CliqHub. See Authentication.
Authorizations
Not needed from the same machine. From another host: a dispatch JWT CliqHub signed for this daemon, or a cliq_tok_… personal token whose user is in the daemon's realm.
Body
Team scope (org namespace)
1Team slug
1Team manifest (YAML)
1Dependency manifest
1Dockerfile shipped with the team
1Role files (roles/*.md)
Hub visibility
draft, public, private Release note
1Hub registry override
1Publish over an existing version
Validate without publishing