Integrations

Automate publishing Live Updates from your CI/CD pipeline. The setup is the same across providers — only the pipeline syntax differs.

• GitHub Actions

  ---

  Set up

• GitLab CI/CD

  ---

  Set up

• Azure DevOps

  ---

  Set up

• Bitbucket Pipelines

  ---

  Set up

How it works

Every pipeline follows the same shape:

1. Authenticate — create an API token in Capawesome Cloud, store it as a CI secret, and log in with --token.
2. Create the channel — apps:channels:create --ignore-errors is idempotent: it creates the channel on first run and is a no-op afterward.
3. Build and publish — let Capawesome Cloud build your web assets in the cloud (apps:builds:create --platform web) so every release uses the same environment, or build on the runner and upload with apps:liveupdates:upload.

A few recommendations that apply to every provider:

• Build in the cloud rather than on the runner, to avoid environment drift.
• Pin the CLI version (@capawesome/cli@<version>) so pipelines are reproducible.
• Use --git-ref to associate each bundle with the commit it was built from.
• Prefer manual dispatch over auto-on-merge so updates ship when you decide.

For signing, versioned channels, and gradual rollouts in CI, see Sign your bundles, Subscribe to a channel, and Roll out gradually.