@better-update/cli 0.41.0 → 0.41.1

package/dist/index.mjs

@@ -35,7 +35,7 @@ var __require = /* @__PURE__ */ createRequire(import.meta.url);
 
 //#endregion
 //#region package.json
-var version = "0.41.0";
+var version = "0.41.1";
 
 //#endregion
 //#region src/lib/interactive-mode.ts
@@ -20081,6 +20081,50 @@ const initGitRepo = (stagingRoot) => Effect.tryPromise({
 	catch: (cause) => new StagingError({ message: `Failed to init git repo in staging dir: ${formatCause(cause)}` })
 }).pipe(Effect.asVoid);
 /**
+* Snapshot the staged tree as a single commit so its working tree reads CLEAN.
+*
+* EAS stages via `git clone` + checkout, so the tree it hands to
+* `expo prebuild --clean` is a clean checkout. Our `cp` + `git init` leaves
+* every staged file UNTRACKED, which `expo prebuild`'s git check reads as
+* "dirty" (`git status --porcelain` is non-empty). Because the native build
+* runs inside a PTY, Expo's `isInteractive()` is true even with no real
+* controlling TTY, so it prompts `Continue with uncommitted changes?` and then
+* blocks on stdin we never write — hanging CI / backgrounded / piped builds.
+*
+* Committing once here makes `git status` clean, so Expo's check passes on
+* EVERY Expo version — the `EXPO_NO_GIT_STATUS` env gate the build sets only
+* exists in newer Expo — with no global `CI=1` side effects. The real
+* dirty-tree decision already ran against the user's *actual* working tree in
+* `ensureRepoClean` (honoring `--allow-dirty`). Best-effort: hooks are disabled
+* and a failure is non-fatal — the build proceeds and `EXPO_NO_GIT_STATUS`
+* still covers newer Expo.
+*/
+const commitStagingSnapshot = (stagingRoot) => Effect.tryPromise(async () => {
+	const run = async (args) => execFileAsync$1("git", [...args], {
+		cwd: stagingRoot,
+		env: {
+			...process.env,
+			LEFTHOOK: "0",
+			HUSKY: "0"
+		}
+	});
+	await run(["add", "-A"]);
+	await run([
+		"-c",
+		"user.name=better-update",
+		"-c",
+		"user.email=build@better-update.dev",
+		"-c",
+		"commit.gpgsign=false",
+		"commit",
+		"--no-verify",
+		"--allow-empty",
+		"-q",
+		"-m",
+		"better-update staging snapshot"
+	]);
+}).pipe(Effect.ignore);
+/**
 * Install args per package manager, frozen-lockfile variants matching EAS
 * (`bun install --frozen-lockfile` / `npm ci --include=dev` / etc.) so the
 * staged install resolves exactly what the user's lockfile pins.
@@ -20136,6 +20180,7 @@ const prepareStagingProject = (input) => Effect.gen(function* () {
 			env: commandEnv
 		});
 	} else yield* printHuman("No package.json at the staging root — skipping dependency install.");
+	yield* commitStagingSnapshot(stagingRoot);
 	return {
 		stagingRoot,
 		projectRoot,