Pear DocsRelease & distribute your app
Build, sign, deploy, and multisig a Pear app: distributables, manual stage → provision, quorum signing, CI, changelogs, and migration.
Everything for shipping a Pear app to users and keeping it updated over the air. For the conceptual picture behind the flow, see Release pipeline.
CI/CD with GitHub Actions
Build, sign, and publish a Pear app from CI so shipping is a git push.
Build & package
Produce signed distributables, standalone binaries, and app-store packages.
Manual deployment
The full-control stage → provision release flow, plus release troubleshooting.
Multisig
Set up quorum signing and run the production multisig release flow.
Publish a changelog for your app
Ship a CHANGELOG.md so users read release notes over peer-to-peer with pear changelog.
Migrate from pear run to Pear OTA
Move off the removed pear run runtime and global Pear API onto Pear OTA (pear-runtime).