* move components to sdk and refactor a way from tamagui
* linting
* reverting since this is just a local issue for me
* lint
* simple
* yarn
* yolo
* run yarn nice
* fix pipelines
* fix tests
* fix mock
* add fonts to mobile sdk
* more feedback
---------
Co-authored-by: Justin Hernandez <justin.hernandez@self.xyz>
* Add mobile SDK demo E2E workflow
* ci: build common before mobile sdk demo e2e
* Fix private pod access for mobile SDK demo e2e
* downgrade react-native-svg
* test fixing android e2e
* fix lock files
* update android e2e terst
* let's not figure out the emulator here. skip
* fix issues
* chore(app): tighten types across app workspace
* fixes
* save wip
* save wip linting
* fix any types
* fix types
* fix: import forwardRef directly from react
- Changed from React.forwardRef to forwardRef import
- Resolves linting warning about named exports
* save typing and linting updates
* cr feedback. final pass
* more cr feedback
* pipeline fixes
* feat: update particular circuit type
* feat: script to build single circuit
* feat: update single circuit build artifact
* feat: support for multiple circuit name build
* wip
* move colors
* sort the dev screen menu alphabetically. for sanity
* lint
* move country hooks to sdk
* added peer dep
* add as dev dep
* remove SelfMobileSdk component before someone thinks that it should be used
* mock it like before
* chore: bump iOS build number to 179
* fix: use PR source commit for deployment to get correct version.json
When deploying from a PR merge (e.g., dev → staging), now uses the source
branch's commit instead of always checking out staging. This ensures
version.json has the correct bumped build number from the previous
deployment's PR back to dev, preventing 'build number already exists' errors.
* downgrade to match store
* fix: use merge_commit_sha instead of head.sha for deployments
Use github.event.pull_request.merge_commit_sha instead of head.sha to ensure
we deploy exactly what landed on staging after the merge, not just the source
branch state. This correctly handles:
- Conflict resolutions made during merge
- Any staging-only changes
- The actual state of staging post-merge
The merge commit still includes the updated version.json from the source
branch (e.g., dev), so build numbers remain correct while ensuring we deploy
and tag the true staging state.
Co-authored-by: CodeRabbit <hello@coderabbit.ai>
---------
Co-authored-by: CodeRabbit <hello@coderabbit.ai>
* chore: bump iOS build number to 179
* fix: use PR source commit for deployment to get correct version.json
When deploying from a PR merge (e.g., dev → staging), now uses the source
branch's commit instead of always checking out staging. This ensures
version.json has the correct bumped build number from the previous
deployment's PR back to dev, preventing 'build number already exists' errors.
* downgrade to match store
* fix: use merge_commit_sha instead of head.sha for deployments
Use github.event.pull_request.merge_commit_sha instead of head.sha to ensure
we deploy exactly what landed on staging after the merge, not just the source
branch state. This correctly handles:
- Conflict resolutions made during merge
- Any staging-only changes
- The actual state of staging post-merge
The merge commit still includes the updated version.json from the source
branch (e.g., dev), so build numbers remain correct while ensuring we deploy
and tag the true staging state.
Co-authored-by: CodeRabbit <hello@coderabbit.ai>
---------
Co-authored-by: CodeRabbit <hello@coderabbit.ai>
