From 637342cb9209e1bd5a560946cba1cf768987a956 Mon Sep 17 00:00:00 2001
From: talksik <patel.arjun50@gmail.com>
Date: Tue, 14 Apr 2026 20:39:51 -0700
Subject: [PATCH] prevent remote release

---
 js/forge.config.ts | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/js/forge.config.ts b/js/forge.config.ts
index 06d32e4..9b6ccd3 100644
--- a/js/forge.config.ts
+++ b/js/forge.config.ts
@@ -41,7 +41,13 @@ const config: ForgeConfig = {
   rebuildConfig: {},
   makers: [
     new MakerSquirrel((arch) => ({
-      remoteReleases: `https://storage.googleapis.com/flowy-releases/llink/win32/${arch}`,
+      // `remoteReleases` is only useful when producing delta packages against a
+      // previously-published build. During a plain `make` (no publish), Squirrel
+      // fetches this URL and fails with a 404 if nothing has been uploaded yet.
+      // Gate it on SQUIRREL_REMOTE_RELEASES=1 which the publish workflow sets.
+      ...(process.env.SQUIRREL_REMOTE_RELEASES === '1' ? {
+        remoteReleases: `https://storage.googleapis.com/flowy-releases/llink/win32/${arch}`,
+      } : {}),
       // Windows code signing via Azure Trusted Signing. Dormant unless the workflow
       // provisions the dlib + metadata file and exports these env vars, so local
       // `yarn make` and unsigned CI builds both work unchanged.