Przejdź do treści
Biblioteka skilli
DevOps i chmura · Budowanie i kod

windows-release

/windows-release

Buduje i weryfikuje instalator Windows NSIS wraz z plikiem latest.yml do wydania aplikacji desktopowej.

Repozytorium
alca-bots ↗
Licencja
Apache-2.0
Ostatnia zmiana repozytorium
09.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
1
Przestarzałość

Brak sygnałów. Repozytorium zmienione 09.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

Co robi i kiedy

Buduje i weryfikuje instalator Windows NSIS wraz z plikiem latest.yml do wydania aplikacji desktopowej.

Oryginalny opis (EN)

Build and verify the Windows desktop build (NSIS installer + latest.yml) for the canonical AlcaBots release and its legacy updater mirror. Use when cutting a release, shipping a new version to Windows users, or when a Windows user reports they are stuck on an old version. Windows only — does not cover the macOS dmg/notarization flow.

Jak działa

  1. Preconditions
  2. 1. Version
  3. 2. Build
  4. 3. Verify before uploading
  5. 4. Publish
  6. Every release ships both
  7. Known: the build is unsigned
Sekcje z nagłówków SKILL.md, w oryginale · 135 linii, 809 słów
Podgląd SKILL.md
---
name: windows-release
description: Build and verify the Windows desktop build (NSIS installer + latest.yml) for the canonical AlcaBots release and its legacy updater mirror. Use when cutting a release, shipping a new version to Windows users, or when a Windows user reports they are stuck on an old version. Windows only — does not cover the macOS dmg/notarization flow.
---

# Windows release

Ships `AlcaBots-<version>-setup.exe` and its update feed to
[ihsieh31/alca-bots](https://github.com/ihsieh31/alca-bots/releases).
The unified release workflow mirrors the same bytes to the legacy releases
repository for apps installed before the updater migration.

**Scope: Windows only.** The macOS build is a separate flow (dmg + notarytool +
staple) that must run on a Mac. This skill never touches mac artifacts — but see
[Every release ships both](#every-release-ships-both) before you finish.

## Preconditions

- **Run on Windows.** NSIS packaging from macOS needs Wine; don't.
- **Node 24+** (`package.json` `engines`). Node 23 builds fine but pnpm warns on
  every step and CI runs 24 — don't debug a runtime oddity on the wrong major.
- **pnpm** via `corepack pnpm`. If `corepack enable` fails with EPERM (no admin),
  drop a `pnpm.cmd` shim containing `@echo off` / `corepack pnpm %*` somewhere on
  PATH — `package:win` chains `pnpm build && …` and needs bare `pnpm` to resolve.

## 1. Version

Bump `version` in `package.json`. It must match the tag on the GitHub release you
upload to, and it becomes the version electron-updater compares against.

## 2. Build

```powershell
pnpm install
pnpm typecheck
pnpm package:win
```

`package:win` deliberately omits `build:speech` — the dictation helper is a signed
macOS Swift binary and has no Windows counterpart.

Output in `release/`:

| File | Purpose |
|---|---|
| `AlcaBots-<version>-setup.exe` | the installer |
| `latest.yml` | **the update feed** — see step 4 |
| `AlcaBots-<version>-setup.exe.blockmap` | differential updates |
| `AlcaBots-<version>-x64.zip` | portable, not used by the updater |

## 3. Verify before uploading

Three things silently produce a broken app if wrong. Check all three:

```powershell
Test-Path release\win-unpacked\resources\server\index.js   # harness server
Test-Path release\win-unpacked\resources\ui\index.html     # built UI
Get-Content release\win-unpacked\resources\app-update.yml  # feed config
```

- Missing `server/index.js` → `utilityProcess.fork` fails → the 🐭 "Couldn't start
  the bot server" page.
- Missing `ui/index.html` → server has nothing to serve → black window.
- `app-update.yml` must point at `ihsieh31/alca-bots` and, while the
  build is unsigned, **must not contain `publisherName`** — electron-updater would
  reject every update as untrusted.

Then smoke-test the installer itself. Run it, and confirm:

1. It installs per-user with no UAC prompt and launches.
2. The chat window renders (not the error page). Server logs land in
   `%APPDATA%\AlcaBots\logs\server.log`.
3. The model picker lists at least one provider — this exercises the `.cmd`-shim
   resolution in `server/procs.ts`, which only ever runs for real on Windows.
4. No update popup appears on launch. Background check failures are silent by
   design; a popup here means that regressed.

## 4. Publish

Upload to the **same tag** as the macOS release for that version, so one release
carries both platforms.

```powershell
Copy-Item release/AlcaBots-<version>-setup.exe release/AlcaBots-setup.exe
gh release upload v<version> --repo ihsieh31/alca-bots `
  release/AlcaBots-<version>-setup.exe `
  release/AlcaBots-setup.exe `
  release/AlcaBots-<version>-setup.exe.blockmap `
  release/latest.yml
```

Prefer the repository's **Release** workflow, which builds all platforms from
one pinned commit and mirrors the complete, byte-identical asset set safely.
If this emergency manual path is used, the same four files must also be attached
to the matching draft in `ihsieh31/alca-bots`; never replace the
bytes of an already-published asset.

Both names are required, for different consumers:

- **`AlcaBots-<version>-setup.exe`** is what `latest.yml` references by name and
  sha512. The auto-updater downloads exactly this.
- **`AlcaBots-setup.exe`** is a byte-identical copy that gives the README's
  `/releases/latest/download/AlcaBots-setup.exe` button a stable URL. This
  mirrors `AlcaBots.dmg` sitting beside `AlcaBots-<version>.dmg`.

### latest.yml is not optional

Without it every installed Windows app 404s on check and stays on its version
forever. It is generated by `package:win` even under `--publish never`.

**Never hand-edit it or carry one forward from a previous build.** It pins the
installer's sha512; a mismatch makes the updater download and then reject the
update, which looks like "updates silently do nothing".

## Every release ships both

A version that exists on macOS but not on this release is a Windows user stuck on
old code with no signal that anything is wrong — the updater reports "up to date"
because `latest.yml` still describes the older build.

So: **whenever a new version goes out, this flow runs too.** If Windows can't ship
for some reason, don't publish the mac-only release under a new version tag either
— or accept that Windows is knowingly frozen and say so in the release notes.

Because the two builds must run on two machines, the tag is the join point: cut the
release, attach mac artifacts from the Mac, attach Windows artifacts from here.

## Known: the build is unsigned

No certificate is configured, so SmartScreen shows "unknown publisher" and users
click **More info → Run anyway**. The README documents this. Auto-update still
works *because* it's unsigned (no `publisherName` to verify against).

If signing is added later, it goes under `win.signtoolOptions` or
`win.azureSignOptions` in `electron-builder.yml` — electron-builder 26 nests these;
there is no top-level `win.certificateFile`. Once signed, keep the certificate
subject stable forever, or list both old and new in `publisherName`; changing it
strands every already-installed user.

Wersje

RepozytoriumWynikLicencja
Ta strona · ihsieh31/alca-bots100Apache-2.0
hamedharami-hub/openmausbot-persian-overlay100Apache-2.0

Migawka bazy z 13.11.2026 · wersja paczki 8964f4ff33e9 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100release-ttokttak
    Przygotowuje wydanie aplikacji Ttokttak, podbija wersję, tworzy instalator Windows i wydanie na GitHub, a także pisze notatki dla okna aktualizacji.
  • 93build-release
    Buduje i wydaje pakiet wtyczek Rook jako instalator Windows, z podbijaniem wersji semver.
  • 86release
    Przygotowuje wydanie Roastpilot: wybiera wersję, pisze changelog i tag, a GitHub Actions buduje instalatory.
  • 98socai-release
    Tworzy, monitoruje i sprawdza wydania aplikacji socai na GitHubie przez gh, w tym przebiegi workflowów i pliki DMG dla macOS.
  • 95haarness-release
    Buduje, sprawdza i publikuje wydania CLI, aplikacji desktop i routera Haarness na macOS, Linuksie i Windows oraz wdraża chmurę na staging i produkcję.
  • 98github-desktop-release
    Kwalifikuje instalatory Windows w GitHub Actions i publikuje zweryfikowane zasoby Windows i macOS z jednego zamrożonego SHA w wydaniu GitHub Release.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.