From 66e7529de530b695df15cfed4febee9b654b4e5c Mon Sep 17 00:00:00 2001 From: Jubarte Date: Sat, 4 Jul 2026 18:42:41 -0300 Subject: [PATCH] fix(beta): publish testing.yml so beta channel is isolated from stable MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit electron-builder's GitHub provider ignores the version-derived channel, so every build published latest.yml — making beta installs read the stable manifest. Force channel=testing on the publish config for beta builds so the update manifest is testing.yml, keeping the channels fully isolated. Co-Authored-By: Claude Opus 4.8 Claude-Session: https://claude.ai/code/session_01FuiQzy1C9jUSQ294rfNtQo --- .github/workflows/release-beta.yml | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/.github/workflows/release-beta.yml b/.github/workflows/release-beta.yml index b5ab2cb..6250ce3 100644 --- a/.github/workflows/release-beta.yml +++ b/.github/workflows/release-beta.yml @@ -159,6 +159,15 @@ jobs: - name: Install dependencies run: npm ci + # electron-builder's GitHub provider ignores the version-derived channel, + # so every build would otherwise publish `latest.yml`. Force the update + # manifest onto the isolated `testing.yml` channel for beta builds. (The + # stable workflow does NOT do this, so it keeps writing `latest.yml`.) + - name: Force beta update channel (testing.yml) + shell: bash + run: | + node -e "const fs=require('fs'),yaml=require('js-yaml');const f='electron-builder.yml';const c=yaml.load(fs.readFileSync(f,'utf8'));const arr=Array.isArray(c.publish)?c.publish:[c.publish];arr.forEach(p=>{if(p&&p.provider==='github')p.channel='testing';});c.publish=arr;fs.writeFileSync(f,yaml.dump(c));console.log('electron-builder.yml publish channel set to testing');" + - name: Build renderer run: npm run build