Add a weekly + manual release-dryrun workflow that exercises the full store pipeline without publishing: Android validates the AAB against Google Play (validate_only), iOS builds a fully signed archive via match (readonly) and skips the App Store upload. Both Fastlane lanes gain a dry_run option that reuses the real release path so the dry-run stays faithful to it. Also add release-mode compile checks (flutter build apk/ios --release) to CI and PR checks to catch release-only breakage, pinning the JDK to match the release toolchain. Trim ci.yml from a redundant 3-OS matrix to two purpose-built jobs (analyze/test once on Linux, iOS build on macOS). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| metadata | ||
| Appfile | ||
| Deliverfile | ||
| Fastfile | ||
| Matchfile | ||
| README.md | ||
fastlane documentation
Installation
Make sure you have the latest version of the Xcode command line tools installed:
xcode-select --install
For fastlane installation instructions, see Installing fastlane
Available Actions
iOS
ios release
[bundle exec] fastlane ios release
Push a new release build to the App Store
This README.md is auto-generated and will be re-generated every time fastlane is run.
More information about fastlane can be found on fastlane.tools.
The documentation of fastlane can be found on docs.fastlane.tools.