* fix: correct Android AAB path and iOS TestFlight distribution settings
Android fix:
- Change AAB path from '../android/...' to 'android/...'
- The gradle task runs with project_dir: 'android/' from app/ directory
- So the AAB is created at app/android/app/build/outputs/bundle/release/
- The path should be relative to app/ not app/fastlane/
iOS fix:
- Remove distribute_external: true and groups for internal track
- Internal TestFlight builds cannot use external distribution
- Internal testers are managed in App Store Connect, not via groups
- This fixes 'Cannot add internal group to a build' error
Both issues were preventing successful deployments after PR merges.
* fix: update iOS build number to sync with TestFlight
- TestFlight already has build 151 (manually deployed by team)
- Update version.json to 151 so pipeline will increment to 152
- This prevents 'build number must be greater' error
* fix: update Gemfile.lock to resolve Android build failure
- Bundle install updated nokogiri and other dependencies
- Fixes 'Gemfile.lock is out of date' error in CI
- This was blocking Android builds in GitHub Actions
* fix: correct Android AAB path and iOS TestFlight distribution settings
Android fix:
- Change AAB path from '../android/...' to 'android/...'
- The gradle task runs with project_dir: 'android/' from app/ directory
- So the AAB is created at app/android/app/build/outputs/bundle/release/
- The path should be relative to app/ not app/fastlane/
iOS fix:
- Remove distribute_external: true and groups for internal track
- Internal TestFlight builds cannot use external distribution
- Internal testers are managed in App Store Connect, not via groups
- This fixes 'Cannot add internal group to a build' error
Both issues were preventing successful deployments after PR merges.
* fix: update iOS build number to sync with TestFlight
- TestFlight already has build 151 (manually deployed by team)
- Update version.json to 151 so pipeline will increment to 152
- This prevents 'build number must be greater' error
Android fix:
- Change AAB path from '../android/...' to 'android/...'
- The gradle task runs with project_dir: 'android/' from app/ directory
- So the AAB is created at app/android/app/build/outputs/bundle/release/
- The path should be relative to app/ not app/fastlane/
iOS fix:
- Remove distribute_external: true and groups for internal track
- Internal TestFlight builds cannot use external distribution
- Internal testers are managed in App Store Connect, not via groups
- This fixes 'Cannot add internal group to a build' error
Both issues were preventing successful deployments after PR merges.
- Remove incorrect instantiation of VersionManager module with .new
- VersionManager is a module (not a class) designed only for build number operations
- Use npm version for semantic version bumps (major/minor/patch) as intended
- Build numbers are already handled in prepare_ios_build/prepare_android_build
Root cause: VersionManager.bump_version() method doesn't exist - the module only
provides bump_ios_build_number() and bump_android_build_number() for build operations.
Semantic versioning must be handled through npm version command.
This fixes the NoMethodError that was causing deployment failures after PR merges.
* fix: add required permissions to mobile-deploy-auto workflow
- Add contents: write and pull-requests: write permissions
- This allows the workflow to call mobile-deploy.yml with proper permissions
- Fixes the startup failure when PR is merged
* test: validate CI/CD pipeline with permissions fix
- Update test comment to trigger build
- This should now work with the fixed permissions
- Expecting deployment to internal track
- Add contents: write and pull-requests: write permissions
- This allows the workflow to call mobile-deploy.yml with proper permissions
- Fixes the startup failure when PR is merged
* fix: correct workflow syntax for reusable workflows
- Split deploy job into deploy-ios and deploy-android
- Fixed platforms output to use JSON array format
- Resolves startup_failure error
* fix: update mobile-deploy.yml to support workflow_call events
- Remove github.event_name == 'workflow_dispatch' conditions
- Use inputs context directly which works for both workflow_dispatch and workflow_call
- Update deployment status messages to show input parameters
- This allows mobile-deploy-auto.yml to successfully trigger deployments
* fix: correct job dependencies and input references in mobile-deploy.yml
- Fix create-release-tags job to depend on 'update-version' not 'update-version-files'
- Change github.event.inputs.test_mode to inputs.test_mode for workflow_call compatibility
- Remove redundant workflow_dispatch check in production condition
- Fix test_mode comparison to use boolean instead of string
- This resolves the workflow validation errors
nokogiri is a native extension gem that causes build failures in CI
environments due to Ruby version conflicts and missing native dependencies.
This restores the conditional exclusion for CI while keeping it available
for local development.
- Regenerated Gemfile.lock with GITHUB_ACTIONS=true to match the conditional
nokogiri exclusion in the Gemfile
- Removes nokogiri and its dependencies (mini_portile2, racc) from lock file
- Fixes pipeline error about deleted nokogiri dependency
* feat: add version management system with build number tracking
- Add version.json to track iOS/Android build numbers separately
- Create version.cjs script for build number management
- Add Fastlane version_manager.rb helper
- Keep npm version for semver, version.json for build tracking
* feat: integrate version.json with Fastlane deployment process
## What Changed
- Updated iOS and Android Fastlane lanes to use version.json for build number management
- Added automatic build number increment on deployment
- Added deployment timestamp tracking
## How It Works
### iOS Deployment
1. Reads current build number from version.json
2. Increments iOS build number (e.g., 148 → 149)
3. Updates Xcode project with new build number via increment_build_number
4. Proceeds with TestFlight deployment
5. Updates lastDeployed timestamp on successful upload
### Android Deployment
1. Reads current build number from version.json
2. Increments Android build number (e.g., 82 → 83)
3. Updates build.gradle with new version code via increment_version_code
4. Proceeds with Play Store deployment
5. Updates lastDeployed timestamp on successful upload
## Why This Change
- Eliminates manual version/build number entry
- Prevents version conflicts between deployments
- Provides single source of truth for build numbers
- Enables automatic deployments without human intervention
- Tracks deployment history with timestamps
## Dependencies
- Requires version.json file (already created in previous commit)
- Uses existing Fastlane plugins:
- increment_build_number (iOS - built-in)
- increment_version_code (Android - from plugin)
- Version numbers still managed by npm version command
* feat: enhance deploy confirmation with version.json info
* fix: use ENV variable directly in increment_build_number to avoid secret masking
* fix: correct xcodeproj path for GitHub Actions workflow
* feat: add test mode to workflow for safe testing
- Skip store uploads when test_mode is true
- Test version bumps and builds without deployment
- Prevent accidental pushes to TestFlight/Play Store
* fix: use gradle_file_path instead of gradle_file for increment_version_code
* fix: use gsub to remove ../ prefix for CI compatibility
* chore: remove accidentally committed files
- Remove .cursor/mcp.json
- Remove .cursorignore
- Remove deployment-automation-summary.md
- Remove deployment-meeting-questions.md
- Remove pipeline.md
* feat: auto-commit version.json after successful deployment
- Commits version.json changes back to repository
- Only runs when test_mode is false
- Uses [skip ci] to prevent infinite loops
- Checks for actual changes before committing
* feat : update package.json in build step using npm version
* feat: add comprehensive caching to mobile deployment workflow
- Add caching for Yarn dependencies, Ruby gems, CocoaPods, Gradle, and Android NDK
- Implement cache versioning strategy for easy cache invalidation
- Fix cache order: caches now restored after checkout but before dependency installation
- Update mobile-setup action to skip installs when dependencies are cached
- Add cache size monitoring to track usage against GitHub's 10GB limit
- Fix Slack notification bug: skip notifications in test_mode
- Add detailed logging for package.json version updates (show from/to versions)
Expected performance improvement: ~50% faster builds (from ~15min to ~7-10min)
* fix: move bundler config after Ruby setup in mobile-setup action
* fix: rename cache env vars to avoid Yarn conflicts
Yarn was interpreting YARN_CACHE_VERSION as its own config setting.
Prefixed all cache version env vars with GH_ to avoid conflicts.
* fix: remove bundler deployment mode to allow Gemfile updates
The deployment mode was causing bundler to fail when Gemfile
changed (nokogiri was removed). CI should be able to update
the lockfile as needed.
* feat: implement strict lock file enforcement (Option 1)
- Re-enable bundler deployment mode for strict Gemfile.lock checking
- Use yarn install --immutable for strict yarn.lock checking
- Add clear error messages when lock files are out of date
- Add pre-checks to verify lock files exist
- This ensures reproducible builds and makes caching maximally effective
When developers change dependencies, they must now:
1. Run yarn install or bundle install locally
2. Commit the updated lock files
3. CI will fail with helpful instructions if they forget
* fix: update Gemfile.lock for CI environment
Remove nokogiri from Gemfile.lock since it's excluded in CI
environments (GITHUB_ACTIONS=true). This allows the strict
lock file checks to pass in CI.
* fix: correct yarn.lock path for monorepo workspace
The project uses Yarn workspaces with yarn.lock at the repository
root, not in the app directory. Updated paths to check for yarn.lock
at workspace root and use it for cache keys.
* fix: handle both boolean and string test_mode parameter
The test_mode parameter was only checking for string 'true' but
could be passed as boolean true from command line. Now handles both
cases to ensure test mode works correctly for iOS and Android.
* fix: address code review feedback for mobile deployment workflow
- Replace jq with Node.js for version extraction (jq not available on macOS runners)
- Fix concurrent commit race condition by creating separate update-version job
- Add platform validation to version_manager.rb and version.cjs scripts
- Use POSIX-compatible single = for shell string comparisons
- Ensure single atomic commit when deploying to both platforms
* fix: formatting and linting issues
- Remove trailing spaces from workflow YAML file
- Fix prettier formatting in JavaScript files
- Add -y flag to yarn version command for non-interactive mode
- Address all lint warnings from CI
* feat: implement automated branch-based mobile deployments
- Add mobile-deploy-auto.yml workflow that triggers on PR merges to dev/main
- Update mobile-deploy.yml to support workflow_call for reusability
- Add deployment_track, version_bump, and auto_deploy parameters
- Create new Fastlane lanes (deploy_auto) for iOS and Android
- Implement smart version bumping based on PR labels (major/minor/patch)
- Add graceful error handling for Play Store permission issues
- Enhance Slack notifications with deployment track information
This enables automatic deployments when PRs are merged:
- dev branch → internal testing track
- main branch → production track
- Skip deployment with [skip-deploy] in PR or no-deploy label
* feat: add automated git tagging and release system
- Add automatic git tagging for production deployments (v2.5.5, platform-specific tags)
- Create GitHub releases with changelogs for production deployments
- Add manual release script (yarn release) for version bumping and tagging
- Implement simple changelog generation from git history
- Add comprehensive deployment documentation in .github/MOBILE_DEPLOYMENT.md
- Update app/README.md with deployment commands and workflows
This completes the release automation system requested in the ticket for
manual tagging and versioning with automated changelogs and release notes.
---------
Co-authored-by: Jayaditya Gupta <nightmare@Jayadityas-MacBook-Pro.local>
