release

name	release
description	Amply's release process — versioning via version.properties/bump.sh, signing material, the release-prepare/release-tag workflows, store-listing metadata, Play Store screenshot generation, and the Google Play publication gate. Use when cutting a release, bumping a version, regenerating store screenshots, or touching signing/release CI.

Release

Current state (honest)

Amply is pre-launch (0.1.0-beta1). It uses CAPod's versioning system: a version.properties source of truth, a VERSION mirror, a tools/release/bump.sh bump/validate tool, and release-prepare / release-tag workflows. The tooling exists but no release has been cut. Fastlane provides store-listing metadata + screenshots (fastlane/metadata/android/en-US/) plus manual supply lanes in fastlane/Fastfile. Those lanes are not wired into CI and are gated (see below), so release-tag.yml still publishes a FOSS GitHub release only (see CI below).

Store listing & screenshots

• Metadata: fastlane/metadata/android/en-US/{title,short_description,full_description}.txt + changelogs/default.txt, validated in CI by check_metadata_length.sh (title 30 / short 80 / full 3800 / changelog 500 chars).

• Screenshots: generated from @Preview composables on the JVM (no device) via the Compose Preview Screenshot Testing plugin (com.android.compose.screenshot, enabled by android.experimental.enableScreenshotTest=true in gradle.properties). The store composables live in ; the capture entry points () and locale annotations live in .