chore: update upstream to v8.0.0

.cursorrules

@@ -0,0 +1,147 @@
+# React Native/Expo Project
+
+You are an expert in TypeScript, React Native, Expo, and Mobile UI development with Nativewind.
+
+Every time you choose to apply a rule(s), explicitly state the rule(s) in the output. You can abbreviate the rule description to a single word or phrase.
+
+## Project Context
+
+## Code Style and Structure
+
+- Write concise, technical TypeScript code with accurate examples
+- Use functional and declarative programming patterns; avoid classes
+- Prefer iteration and modularization over code duplication
+- Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError)
+- Ensure components are modular, reusable, and maintainable.
+- Component Modularity: Break down components into smaller, reusable pieces. Keep components focused on a single responsibility and shouldn't be more than 80 lines of code.
+- To install new packages use `npx expo install <package-name>`
+- Structure repository files as follows:
+
+```
+src
+  ├── api   ## API related code, mainly using axios and react query
+  ├── app   ## the main entry point for expo router(file-based routing), when you can find screens and navigation setup
+  ├── components  ## shared components
+  │   ├── card.tsx
+  │   └── ui  ## core ui components. buttons, inputs, etc
+  ├── lib  ## shared libraries, auth, env, hooks, i18n, storage, test-utils, utils
+  ├── translations  ## translations files for the app
+  ├── types  ## shared types
+
+```
+
+## Tech Stack
+
+- Expo
+- React Native
+- TypeScript
+- Nativewind ( Tailwind CSS for React Native )
+- Expo Router
+- React Query with React Query Kit
+- Zustand
+- React Native Keyboard Controller
+- React Native SVG
+- React Native MMKV
+
+## Naming Conventions
+
+- Favor named exports for components and utilities
+- Use kebabCase for all files names and directories (e.g., visa-form.tsx)
+
+## TypeScript Usage
+
+- Use TypeScript for all code; prefer types over interfaces
+- Avoid enums; use const objects with 'as const' assertion
+- Use functional components with TypeScript interfaces
+- Define strict types for message passing between different parts of the extension
+- Use absolute imports for all files @/...
+- Avoid try/catch blocks unless there's good reason to translate or handle error in that abstraction
+- Use explicit return types for all functions
+
+## State Management
+
+- Use React Zustand for global state management
+- Implement proper cleanup in useEffect hooks
+
+## Syntax and Formatting
+
+- Use "function" keyword for pure functions
+- Avoid unnecessary curly braces in conditionals
+- Use declarative JSX
+- Implement proper TypeScript discriminated unions for message types
+
+## UI and Styling
+
+- Use Nativewind for styling and components
+- Use built-in ui components such as Button, Input from `@components/ui`
+- Ensure high accessibility (a11y) standards using ARIA roles and native accessibility props.
+- Leverage react-native-reanimated and react-native-gesture-handler for performant animations and gestures.
+- Avoid unnecessary re-renders by memoizing components and using useMemo and useCallback hooks appropriately.
+- Make sure to use defined colors and fonts in the tailwind config file.
+
+Here is a simple example of how a component should be written using :
+
+```tsx
+import * as React from 'react';
+
+import { Text, View, Image, SavaAreaView } from '@/components/ui';
+
+// Props should be defined in the top of the component
+type Props = {
+  text: string;
+};
+
+export function Title({ text }: Props) {
+  return (
+    <View className="flex-row items-center justify-center  py-4 pb-2">
+      <Text className="pr-2 text-2xl">{text}</Text>
+      <View className="h-[2px] flex-1 bg-neutral-300" />
+
+      <Image
+        source={require('@assets/images/demo.png')}
+        style={{ width: 24, height: 24 }}
+        contentFit="contain"
+      />
+    </View>
+  );
+}
+```
+
+## Error Handling
+
+- Log errors appropriately for debugging
+- Provide user-friendly error messages
+
+## Testing
+
+- Write unit tests using Jest and React Native Testing Library.
+- Write unit tests for utilities and complex components
+- The test file should be named like the component file but with the .test.tsx extension (e.g., component-name.test.tsx)
+- Do not write unit tests for simple components that only show data
+
+## Git Usage
+
+Commit Message Prefixes:
+
+- "fix:" for bug fixes
+- "feat:" for new features
+- "perf:" for performance improvements
+- "docs:" for documentation changes
+- "style:" for formatting changes
+- "refactor:" for code refactoring
+- "test:" for adding missing tests
+- "chore:" for maintenance tasks
+
+Rules:
+
+- Use lowercase for commit messages
+- Keep the summary line concise with a maximum of 100 characters
+- Reference issue numbers when applicable
+
+## Documentation
+
+- Maintain clear README with the following sections:
+  - Setup ( how to install and run the project )
+  - Usage ( listing all the commands and how to use them )
+  - Stack ( the tech stack used in the project )
+  - Folder Structure ( the folder structure of the project only the important ones inside src )

.github/workflows/eas-build-prod.yml

@@ -0,0 +1,43 @@
+# 🔗 Links:
+# Source file: https://github.com/obytes/react-native-template-obytes/blob/master/.github/workflows/eas-build-prod.yml
+# Starter releasing process: https://starter.obytes.com/ci-cd/app-releasing-process/
+
+# ✍️ Description:
+# This workflow is used to trigger a build on EAS for Prod environment.
+# Can be triggered manually from the actions tab.
+# This workflow will use ./actions/eas-build action to trigger the build on EAS with production env.
+
+# 🚨 GITHUB SECRETS REQUIRED:
+#         - EXPO_TOKEN: Expo token to authenticate with EAS
+#         - You can get it from https://expo.dev/settings/access-tokens
+
+name: EAS Production Build (Android & IOS) (EAS)
+
+on:
+  workflow_dispatch:
+
+jobs:
+  Build:
+    name: EAS Production Build (Android & IOS) (EAS)
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check for EXPO_TOKEN
+        run: |
+          if [ -z "${{ secrets.EXPO_TOKEN }}" ]; then
+            echo "You must provide an EXPO_TOKEN secret linked to this project's Expo account in this repo's secrets. Learn more: https://docs.expo.dev/eas-update/github-actions"
+            exit 1
+          fi
+
+      - name: 📦 Checkout project repo
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: 📦 Setup Node + PNPM + install deps
+        uses: ./.github/actions/setup-node-pnpm-install
+
+      - name: ⏱️ EAS Build
+        uses: ./.github/actions/eas-build
+        with:
+          APP_ENV: production
+          EXPO_TOKEN: ${{ secrets.EXPO_TOKEN }}

.github/workflows/eas-build-qa.yml

@@ -0,0 +1,47 @@
+# 🔗 Links:
+# Source file: https://github.com/obytes/react-native-template-obytes/blob/master/.github/workflows/eas-build-qa.yml
+# Starter releasing process: https://starter.obytes.com/ci-cd/app-releasing-process/
+
+# ✍️ Description:
+# This workflow is used to trigger a build on EAS for the QA environment.
+# It will run on every GitHub release published on the repo or can be triggered manually from the actions tab.
+# This workflow will use ./actions/eas-build action to trigger the build on EAS with staging env.
+
+# 🚨 GITHUB SECRETS REQUIRED:
+#         - EXPO_TOKEN: Expo token to authenticate with EAS
+#         - You can get it from https://expo.dev/settings/access-tokens
+
+name: EAS QA Build (Android & IOS) (EAS)
+
+on:
+  workflow_dispatch:
+  release:
+    types: [published]
+
+jobs:
+  Build:
+    name: EAS QA Build (Android & IOS) (EAS)
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check for EXPO_TOKEN
+        run: |
+          if [ -z "${{ secrets.EXPO_TOKEN }}" ]; then
+            echo "You must provide an EXPO_TOKEN secret linked to this project's Expo account in this repo's secrets. Learn more: https://docs.expo.dev/eas-update/github-actions"
+            exit 1
+          fi
+      - name: 📦 Checkout project repo
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: 📦 Setup Node + PNPM + install deps
+        uses: ./.github/actions/setup-node-pnpm-install
+
+      - name: ⏱️ EAS Build
+        uses: ./.github/actions/eas-build
+        with:
+          APP_ENV: staging
+          EXPO_TOKEN: ${{ secrets.EXPO_TOKEN }}
+          VERSION: ${{ github.event.release.tag_name }}
+          IOS: false # TODO: set as true when IOS account is ready
+

.github/workflows/expo-doctor.yml

@@ -44,14 +44,28 @@ jobs:
       - name: 📦 Setup Node + PNPM + install deps
         uses: ./.github/actions/setup-node-pnpm-install
 
+<<<<<<< HEAD
       - name: 🚑 Run Doctor Checks
         run: |
           chmod +x .github/scripts/expo-doctor.sh
+=======
+      - name: Run prebuild
+        run: pnpm run prebuild
+
+      - name: 🚑 Run Doctor Checks
+        run: |
+          chmod +x .github/scripts/expo-doctor.sh
+          rm -rf ios android
+>>>>>>> c7bb80d
           .github/scripts/expo-doctor.sh
 
       - name: Add doctor report as comment on PR
         if: github.event_name == 'pull_request' && always()
         uses: marocchino/sticky-pull-request-comment@v2
         with:
           header: expo-doctor
-          path: .expo/expo-doctor.md
+<<<<<<< HEAD
+          path: .expo/expo-doctor.md
+=======
+          path: .expo/expo-doctor.md
+>>>>>>> c7bb80d

.github/workflows/new-app-version.yml

@@ -0,0 +1,65 @@
+# 🔗 Links:
+# Source file: https://github.com/obytes/react-native-template-obytes/blob/master/.github/workflows/lint-ts.yml
+# Starter releasing process: https://starter.obytes.com/ci-cd/app-releasing-process/
+
+# ✍️ Description:
+# This workflow is used to create a new version of the app and push a new tag to the repo.
+# As this workflow will push code to the repo, we set up GitHub Bot as a Git user.
+# This Workflow need to be triggered manually from the Actions tab in the repo.
+#         1. Choose your release type (patch, minor, major)
+#         2. The workflow will run the np-release script which runs the following steps:
+#             - Bump the version in package.json based on the release type using np
+#             - Run the prebuild of the app to align the package.json version with the native code
+#             - Create a new tag with the new version
+#             - Push the new tag to the repo
+#
+
+# 🚨 GITHUB SECRETS REQUIRED:
+#         - GH_TOKEN: A GitHub token with write repo access.
+#           You can generate one from here: https://docs.github.com/en/[email protected]/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens
+#           make sure to add it to the repo secrets with the name GH_TOKEN
+
+name: New App Version
+
+on:
+  workflow_dispatch:
+    inputs:
+      release-type:
+        type: choice
+        description: 'Release type (one of): patch, minor, major'
+        required: true
+        default: 'patch'
+        options:
+          - patch
+          - minor
+          - major
+
+jobs:
+  release:
+    name: Create New Version and push new tag
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      - name: 🔍 GH_TOKEN
+        if: env.GH_TOKEN == ''
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: echo "GH_TOKEN=${GITHUB_TOKEN}" >> $GITHUB_ENV
+      - name: 📦 Checkout project repo
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+          token: ${{ secrets.GH_TOKEN }}
+
+      - name: 📝 Git User Setup
+        run: |
+          git config --global user.email "41898282+github-actions[bot]@users.noreply.github.com"
+          git config --global user.name "github-actions[bot]"
+
+      - name: 📦 Setup Node + PNPM + install deps
+        uses: ./.github/actions/setup-node-pnpm-install
+
+      - name: 🏃‍♂️ Run App release
+        run: |
+          pnpm app-release ${{ github.event.inputs.release-type }}

.github/workflows/new-github-release.yml

@@ -0,0 +1,34 @@
+# 🔗 Links:
+# Source file: https://github.com/obytes/react-native-template-obytes/blob/master/.github/workflows/new-github-release.yml
+# Starter releasing process: https://starter.obytes.com/ci-cd/app-releasing-process/
+
+# ✍️ Description:
+# This workflow will be triggered automatically after the new app version workflow has been executed successfully.
+# It will create a new GitHub release with the new app version and the release notes.
+
+# 🚨 GITHUB SECRETS REQUIRED: None
+
+name: New GitHub Release
+
+on:
+  push:
+    tags:
+      - '*'
+
+jobs:
+  release:
+    name: New GitHub Release
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      - name: 📦 Checkout project repo
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: 🏃‍♂️Create A Draft Github Release
+        uses: ncipollo/release-action@v1
+        with:
+          generateReleaseNotes: true
+          draft: false