* Add tree-shakeable exports
* Migrate imports for tree-shakeable paths
* Document ESM extension requirement
* udpates
* install new lock
* yarn nice
* build deps
* save working index export no wildcard approach
* save wip
* fix building
* add tree shaking doc and examples
* sort package json files
* update package.json
* fix analyzing web
* make sure that web is built
* wip tree shaking
* building works again. save wip logic
* use granular imports
* wip test
* save wip
* Remove hardcoded .d.ts files and setup automatic TypeScript declaration generation
- Remove redundant constants.d.ts, types.d.ts, utils.d.ts files
- Add build:types script to automatically generate TypeScript declarations
- Update tsup config to disable DTS generation (handled separately)
- Update .gitignore to prevent future commits of generated .d.ts files
- Fixes import resolution errors in app by ensuring declarations are always generated
* Add .gitignore rules for generated TypeScript declarations
* ignore dts files
* Remove redundant index.js re-export files
- Remove constants.js, types.js, utils.js as they're redundant with tsup build
- These were just re-exports pointing to dist files that tsup generates
- package.json exports already point directly to built files
- Update .gitignore to prevent future commits of these generated files
- tsup handles all the building, no manual re-export files needed
* save current wip fixes
* add tsup config for web building
* common prettier and fix imports
* prettier
* fix tests
* implement level 3 tree shaking
* improve splitting
* optimize vite web building and prettier
* remove comments
* sort export params
* feedback and fix pipelines
* fix circuit-names path
* fix test
* fix building
* sort
* fix building
* allow cursor to edit scripts
* fix loadDocumentCatalog undefined
* fix build settings
* fix build settings
* additional metro tree shaking
* improved discovery script for xcode building
* pr feedback and fix camelCasing
* simplify shim setup
* fix xcode building and add command to test building
* remove comment
* simplify
- Modified package.json to create separate install commands for iOS and Android
- Updated mobile-setup/action.yml to use platform-specific install commands
- Android builds will no longer try to run pod install and increment ios build number
* test: trigger CI/CD pipeline with harmless comment update
Testing the auto-deploy workflow after recent fixes
* fix: remove duplicate checkout in mobile-setup action
The mobile-setup action was doing its own checkout which could cause
inconsistencies between iOS and Android jobs. The main workflow already
handles checkout, so this duplicate checkout was causing Android builds
to fail with Gemfile.lock errors while iOS passed.
* fix: enable checkout for Android builds
The checkout step was conditionally skipped for Android builds,
causing 'yarn.lock and Gemfile.lock missing' errors. Both iOS
and Android need the repository checked out to access lock files.
* test: trigger CI/CD pipeline with harmless comment update
Testing the auto-deploy workflow after recent fixes
* fix: remove duplicate checkout in mobile-setup action
The mobile-setup action was doing its own checkout which could cause
inconsistencies between iOS and Android jobs. The main workflow already
handles checkout, so this duplicate checkout was causing Android builds
to fail with Gemfile.lock errors while iOS passed.
* 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
