Note that app releases ship plain executables, not installer packages

AI Assisted
This commit is contained in:
jparkerweb committed 2026-10-25 12:51:25 -07:00
1 parent 3155298fea
commit 4d05b4f6f6
2 files changed
+12

No files matched your search

+6
View File
@@ -32,6 +32,12 @@ Releases carry one file per system:
On any other system the installer says there is no build for it and carries on without the app.
Each of those is a plain executable, not an OS-level installer package (no `.msi`, no NSIS `.exe`
setup, no `.dmg` with a drag-to-Applications step): the installer above places it directly, already
verified. `plan2code-app`'s own `npm run build` can produce `.msi`/NSIS/`.dmg`/`.deb` bundles locally
(Tauri's bundler is on), but the release workflow does not build or publish them; nothing today
downloads or runs one.
You also need Node.js 18 or newer (the app checks at start and says what to install) and:
- **Windows:** the WebView2 runtime, which comes with Windows 11 and current Windows 10.
+6
View File
@@ -8,6 +8,12 @@ Work from the pre-release build: publish a GitHub pre-release so `release-app.ym
then install from it. Tick each box per system and note anything that is a rough edge rather than a
failure.
`npm run build` here runs `tauri build` with bundling on, so a local build also produces `.msi`/NSIS
`.exe`/`.dmg`/`.deb` installer packages under `src-tauri/target/release/bundle/`. Ignore those: the
release workflow builds with `--no-bundle` and attaches only the plain executable per system (see
`.github/workflows/release-app.yml`); `install.js` is the only installer, and it places that plain
file directly after checking it against the release's checksum list.
## Before you start
- [ ] `node scripts/check-versions.mjs --tag v<version>` passes (version.json, package.json,