You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# A transient GitHub error during create doesn't necessarily mean the release failed; it may have been created anyway, so a later "already exists" error means it's present.
923
+
if gh release view "${{ needs.prep.outputs.TAG }}" --repo "${{ github.repository }}" &> /dev/null; then
924
+
echo "Release ${{ needs.prep.outputs.TAG }} exists despite a create error (likely a transient 502), treating as success."
925
+
break
926
+
fi
919
927
if [[ $i -lt $CREATE_MAX_RETRIES ]]; then
920
928
echo "Failed to create release. Retrying in 3 seconds... ($((CREATE_MAX_RETRIES - i)) attempts left)"
921
929
sleep 3
@@ -997,6 +1005,68 @@ jobs:
997
1005
}]
998
1006
}
999
1007
1008
+
# Upload the production-bound binary to Sentry for size analysis.
1009
+
# - Cherry-pick deploys build native in this run, so we pull the .aab/.ipa from the build artifact.
1010
+
# - Re-promotion deploys don't build native, so we download from the matching `<TAG>-staging`
1011
+
# GitHub Release populated during the staging deploy of that version.
1012
+
androidUploadSentry:
1013
+
name: Upload Android build to Sentry for size analysis
0 commit comments