Releasing
bellui release builds the app in release mode, packages it, and then does the
signing and store packaging each platform needs. It takes most of the flags of
bellui package (not --src, --exe or --release; it always builds in
release mode), plus the signing details below. Each platform’s own tools
must be installed; the command calls them for you.
bellui release -os darwin --app-id com.example.notes --app-version 1.2.0 \
--profile "Notes Distribution" --category productivity| Flag | Needed | Notes |
|---|---|---|
--profile | Yes | The provisioning profile. |
--category | Yes | A Mac App Store category, such as productivity. An unknown name is rejected with the list of valid ones. |
--certificate | No | Defaults to 3rd Party Mac Developer Application. The matching Installer certificate is used for the package. |
The command signs the app bundle with codesign, builds an installer package
with productbuild, and signs that with productsign. The result is
Name.pkg. You need Xcode’s command line tools and both certificates in your
keychain.
On Linux, BSD and the web, bellui release produces the same files as
bellui package --release; there is no store packaging step.
Like bellui package, a successful release adds one to the build number in
your manifest.