Publish releases from this fork (point auto-update at JeanBaptisteRenard/switchboard)

[ymajoros]

What

One-line change: build.publish.owner doctly → JeanBaptisteRenard in package.json.

Why

build.yml is already a full release pipeline — on a v* tag it builds mac/win/linux(x64+arm64) and the publish job runs gh release create (a draft Release with all binaries attached) in this repo. It's just never been triggered, so there are no releases yet.

The gap: build.publish still points at doctly/switchboard. electron-builder bakes that into the auto-update metadata (latest*.yml / app-update.yml), so an app published from this fork would check doctly for updates — wrong. This points the update channel at the repo that actually hosts the releases.

After merge

Push a v* tag (e.g. bump version and tag v0.0.31) → the workflow cuts a draft release with installable binaries + correct auto-update. The release-upload itself already targets this repo (gh release create uses the running repo's token), so nothing else is needed.

Caveats

• mac/win artifacts are unsigned unless CSC_LINK/CSC_KEY_PASSWORD/APPLE_* secrets are set (users get the usual 'unidentified developer' prompt). Linux AppImage/deb need no signing and are clean.
• This is a fork-divergence from upstream (upstream's publish correctly stays doctly); appropriate since this fork is self-maintained and well ahead of upstream.

[JeanBaptisteRenard]

Reviewed end-to-end (config + the full release pipeline + the auto-update runtime). The one-liner is correct: build.publish.owner governs both the --publish target and the app-update.yml/latest*.yml feed URL baked into the packaged app — pointing it at this repo, which is where build.yml's publish job actually uploads, is exactly right. electron-updater is already fully wired in main.js (checks at T+5s then every 4h), and the latest*.yml metadata files are generated and uploaded. No regression surface for the existing AppImage.

Merging. Two things to flag for when you actually cut the first release (neither blocks this merge):

1. Draft releases are invisible to electron-updater — after a v* tag, the workflow creates a --draft release; you must click "Publish" in the GitHub UI to activate the update feed. (Good thing — it's a review gate before users see the update.)
2. notarize: true + no Apple secrets = the mac build job errors out (not a graceful unsigned fallback), which would block the whole pipeline. I'll send a tiny follow-up flipping notarize to false so the first release can ship unsigned-but-green; you can wire the APPLE_* secrets later if you want signed mac builds.

Nice catch on the auto-update channel pointing at the wrong repo — thanks! 🙏