reapply SENTRY_DIST patch

2026-07-14 15:19:23 +03:00
parent 6127b5d3d7
commit 2e974e11df
4 changed files with 25 additions and 2 deletions
@@ -0,0 +1,14 @@
+diff --git a/cli.js b/cli.js
+index 2a2e6afbd46a6a5182918373d71853193945ff31..44e5888e869003438fc7ef4931b9992f2896a23f 100755
+--- a/cli.js
+++ b/cli.js
+@@ -304,6 +304,9 @@ for (const [assetGroupName, assets] of Object.entries(groupedAssets)) {
+   if (isHermes) {
+     args.push('--debug-id-reference');
+   }
+  if (process.env.SENTRY_DIST) {
+    args.push('--dist', process.env.SENTRY_DIST);
+  }
+   args.push(...assets);
+ 
+   const result = spawnSync(sentryCliBin, args, {
@@ -0,0 +1,7 @@
+# @sentry/expo-upload-sourcemaps patch
+
+Adds `--dist $SENTRY_DIST` to the `sentry-cli sourcemaps upload` call, when the
+env var is set. Symbolication matches on debug IDs so this isn't strictly
+required, but it keeps OTA sourcemap artifacts associated with the commit hash
+(`dist`) in the Sentry UI, matching the runtime `dist` set in
+`src/logger/sentry/setup/index.ts`.