Merge branch 'Expensify:main' into timing-module-deprecate

Author: adhorodyski

.github/workflows/preDeploy.yml

@@ -58,7 +58,12 @@ jobs:
 
       - name: Check if merged pull request should trigger a deploy
         id: shouldDeploy
-        run: echo "SHOULD_DEPLOY=${{ (!fromJSON(steps.isStagingDeployLocked.outputs.IS_LOCKED) && github.actor != 'OSBotify') }}" >> "$GITHUB_OUTPUT"
+        run: |
+          if gh api /orgs/Expensify/teams/mobile-deployers/memberships/${{ github.actor }} --silent; then
+            echo "SHOULD_DEPLOY=${{ (!fromJSON(steps.isStagingDeployLocked.outputs.IS_LOCKED) && github.actor != 'OSBotify') }}" >> "$GITHUB_OUTPUT"
+          else
+            echo "SHOULD_DEPLOY=false" >> "$GITHUB_OUTPUT"
+          fi
 
   skipDeploy:
     runs-on: ubuntu-latest

Mobile-Expensify

@@ -114,8 +114,8 @@ android {
         minSdkVersion rootProject.ext.minSdkVersion
         targetSdkVersion rootProject.ext.targetSdkVersion
         multiDexEnabled rootProject.ext.multiDexEnabled
-        versionCode 1009031115
-        versionName "9.3.11-15"
+        versionCode 1009031117
+        versionName "9.3.11-17"
         // Supported language variants must be declared here to avoid from being removed during the compilation.
         // This also helps us to not include unnecessary language variants in the APK.
         resConfigs "en", "es"

android/app/build.gradle

@@ -124,6 +124,17 @@ Basically, a bad problem statement (ie, a reverse solution statement) is written
 ### Posting Ideas
 Additionally, if you want to discuss an idea with the open source community without having a P/S statement yet, you can post it in #expensify-open-source with the prefix `IDEA:`. All ideas to build the future of Expensify are always welcome! i.e.: "`IDEA:` I don't have a P/S for this yet, but just kicking the idea around... what if we [insert crazy idea]?".
 
+## Working on Sentry Issues
+If you have access to Sentry and are investigating an error, please **assign yourself to the Sentry issue** before starting your investigation. This helps prevent duplicate efforts where multiple contributors spend time investigating the same error independently.
+
+When working on Sentry issues:
+1. **Assign yourself** in Sentry when you start investigating an issue
+2. **Link a GitHub issue** - find or create a GitHub issue for the error, then link it in Sentry using their issue tracking integration
+3. **Document your findings** in the linked GitHub issue
+4. **Update the Sentry issue status** when the fix is merged (mark as resolved with the version number if applicable)
+
+This helps future investigators understand the history and current status of errors, potentially saving hours of duplicate work.
+
 ## Working on Expensify Jobs
 *Reminder: For technical guidance, please refer to the [README](https://github.com/Expensify/App/blob/main/README.md)*.
 

assets/images/home-testdrive-image.png

@@ -44,7 +44,7 @@
 		</dict>
 	</array>
 	<key>CFBundleVersion</key>
-	<string>9.3.11.15</string>
+	<string>9.3.11.17</string>
 	<key>FullStory</key>
 	<dict>
 		<key>OrgId</key>

assets/images/simple-illustrations/simple-illustration__thumbsupstars.svg

@@ -13,7 +13,7 @@
 	<key>CFBundleShortVersionString</key>
 	<string>9.3.11</string>
 	<key>CFBundleVersion</key>
-	<string>9.3.11.15</string>
+	<string>9.3.11.17</string>
 	<key>NSExtension</key>
 	<dict>
 		<key>NSExtensionPointIdentifier</key>

contributingGuides/CONTRIBUTING.md

@@ -2519,7 +2519,7 @@ PODS:
     - ReactCommon/turbomodule/core
     - SocketRocket
     - Yoga
-  - react-native-launch-arguments (4.0.2):
+  - react-native-launch-arguments (4.1.1):
     - React
   - react-native-netinfo (11.4.1):
     - boost

ios/NewExpensify/Info.plist

@@ -13,7 +13,7 @@
 	<key>CFBundleShortVersionString</key>
 	<string>9.3.11</string>
 	<key>CFBundleVersion</key>
-	<string>9.3.11.15</string>
+	<string>9.3.11.17</string>
 	<key>NSExtension</key>
 	<dict>
 		<key>NSExtensionAttributes</key>