PRODUCTION LIFECYCLE
Make release day a repeatable engineering workflow.
Catch missing release inputs early, create verifiable packages, sign the right artifacts, publish through stores and hosts, and leave receipts that CI and teammates can inspect.
# find and run on real devices
fission devices
fission run --target android --device <device-id>
# package the site for any static host
fission package --project-dir documentation \
--target site --format static --release
RELEASE OPERATIONS
The framework should help after the binary builds.
Packaging, signing, release notes, screenshots, credentials, stores, hosting, rollouts, and receipts should be explicit project workflows.
READINESS
Know what is missing
Preflight checks report SDKs, package tools, signing inputs, credentials, store metadata, and artifact shape before release day.
ARTIFACTS
Manifests and receipts
Package outputs carry hashes, sizes, MIME types, targets, formats, validation state, and distribution receipts.
DISTRIBUTION
Stores and hosts
GitHub Releases, static hosting, object storage, Google Play, App Store Connect, and Microsoft Store paths fit one workflow.
POST-BUILD LIFECYCLE
Release readiness is checked before upload.
Fission's release tooling aims to make missing metadata, bad artifacts, absent credentials, and provider-specific gaps visible before they block launch.
PREFLIGHT
Find missing release inputs early
Project checks verify SDKs, package tools, signing references, release metadata, icons, screenshots, credentials, and provider-specific requirements.
Release content
ARTIFACTS
Every output gets a manifest
Packages record target, format, path, hashes, size, MIME type, signing state, cache policy, upload intent, and distribution readiness.
Packaging overview
PROVIDERS
Publish through the right channel
Release flows cover app stores, GitHub Releases, static hosts, Docker registries, and object storage without turning each app into a custom script pile.
Distribution overview
RELEASE PATH
Package artifacts, validate requirements, publish through providers.
01
Package
Produce installable or uploadable artifacts for the selected target.
02
Validate
Check release metadata, screenshots, signing, credentials, and provider requirements.
03
Distribute
Publish to stores, static hosts, package flights, testers, tracks, and rollout channels.
Release work is product work
The CLI gives packaging and distribution the same project model as development instead of leaving each app to invent release scripts.