appflight_cli 0.4.0

AppFlight CLI — upload APKs from your terminal or CI pipelines without the Play Store.

Changelog

0.4.0

• Anonymous usage analytics — the CLI now optionally collects anonymous usage data via GA4 to help improve the tool. You are prompted once on first run; CI environments are always skipped.
• appflight analytics enable — opt in to analytics.
• appflight analytics disable — opt out at any time.
• appflight analytics status — show current opt-in status.

0.3.1

• Kotlin DSL support in appflight upload — version resolution now checks build.gradle.kts before build.gradle, and the regexes handle both Groovy (versionName "x") and Kotlin DSL (versionName = "x") syntax. Fixes React Native 0.77+ projects that use build.gradle.kts by default.

0.3.0

• React Native bare workflow support — appflight init now prompts for your framework (Flutter or React Native) or accepts --project-type flutter|react-native to skip the prompt. React Native projects are validated against package.json + android/app/build.gradle.
• Framework-aware APK paths — React Native uses Gradle output paths (android/app/build/outputs/apk/<flavor>/release/); Flutter paths are unchanged.
• Automatic version from Gradle — React Native uploads read versionName + versionCode from android/app/build.gradle and combine them as 1.2.0+7. Override with --version or --build-number as usual.
• Smarter project root detection — upload now walks up looking for appflight.json instead of pubspec.yaml, so it works from any subdirectory in both Flutter and React Native projects.
• Conditional build hints — the "APK not found" error now shows the correct build command for your framework (flutter build apk vs ./gradlew assemble...).
• All existing Flutter behaviour is fully backward-compatible — projectType defaults to flutter and no changes to existing appflight.json files are required.

0.2.1

• Two-segment package names now allowed in appflight init — the validator previously required at least 3 dot-separated segments (e.g. com.mycompany.myapp). Names like dev.mhmz are now accepted, matching the AppFlight mobile app and backend.

0.2.0

• Rollover uploads — First Class (pro) uploads at the APK cap now auto-drop the oldest build instead of blocking. When a rollover happens, the CLI prints Rolled over oldest build (vX.Y.Z) to stay at your plan cap.
• Higher pro APK caps — Individual First Class: 10 → 15; Organization First Class: 15 → 20.
• Free-tier TTL shortened to 7 days (was 14). First Class keeps 14 days.
• Economy (free) uploads at cap still exit 8 with the existing PLAN_LIMIT message.

0.1.7

• Default environment is now prod (was stage). Pasted keys from the AppFlight mobile app now work out of the box without any APPFLIGHT_ENV override. stage and local remain available via APPFLIGHT_ENV / --env for contributors hacking on the CLI or Cloud Functions.

0.1.6

• Fix appflight --version crashing with PathNotFoundException — version is now read from an embedded Dart constant instead of pubspec.yaml (which is not shipped to ~/.pub-cache/global_packages/).

0.1.5

• Added Paywall guard in cli operations

0.1.4

Patch Changes

• 6e5e541: Fix release pipeline: use PAT for tag push to correctly trigger pub.dev publish

0.1.3

Patch Changes

• 0445a81: Update README to reflect simplified release flow and add issues link

0.1.2

Patch Changes

• 4ec9d2d: Updated docs for pub.dev scoring; added MIT license, example, and unit tests.
• fecf708: bump versioning with docs and pub.dev scores

0.1.1

• --version and --docs flags

0.1.0

• Initial release
• init — scaffold appflight.json in a Flutter project
• login — authenticate with an AppFlight API key
• logout — remove saved credentials
• whoami — display the authenticated user
• upload — upload an APK and notify testers automatically