Skip to content

Publishing

Alejandro Mora edited this page Nov 12, 2026 · 2 revisions

Publishing

Store packages

Script Output
./publish-ios.sh The signed iPhone/iPad .ipa. It refuses the build if any binary carries a slice other than arm64, which App Store Connect rejects.
./publish-mac.sh The signed Mac App Store .pkg (Apple silicon and Intel, sandboxed).
./publish-windows.ps1 The Microsoft Store packages: an unsigned .msix each for x64 and arm64 in artifacts/windows (the Store signs them).
./publish-android.sh The signed Google Play .aab and an .apk. Needs the ANDROID_* keystore variables.
./publish-linux.sh x64 arm64 Self-contained Linux tarballs, Readout.Linux/bin/publish/Readout-linux-<arch>.tar.gz. Runs on macOS and Windows too.
./package-linux.sh 1.2.0 x64 arm64 The .deb and .rpm for each architecture in artifacts/linux, from publish-linux.sh's builds. Runs on Linux with dpkg-deb and rpmbuild.

Upload the Apple packages with Transporter.

Windows

Release Windows builds are MSIX; Debug builds stay a plain .exe. -Test -Install builds and installs a local test copy (needs Developer Mode), and -Wack also runs the Windows App Certification Kit from an administrator shell.

Releasing from a tag

Pushing a tag like v1.2.0 runs .github/workflows/release.yml: it runs the tests, builds every package above with the tag's version, publishes a GitHub release (with the .apk and the Linux tarballs and packages attached) and sends the packages to the stores, each waiting for approval. For a final release it also asks amd989/packages to put the .deb and .rpm on packages.alejandro.md, which needs the PACKAGES_DISPATCH_TOKEN repository secret.

git tag v1.2.0 && git push origin v1.2.0

Details in docs/STORE-CI.md.

The Mac app with the meter and a wide graph

Readout

Home


Developing

Platforms

Reference (in the repo)

Clone this wiki locally