electron-builder.yml

appId: com.smafnan.compound
productName: Compound
directories:
  output: release
  buildResources: build
files:
  - dist/**/*
  - electron/**/*
# Where installed copies look for new versions. This block is what makes
# electron-builder write `app-update.yml` into the app and generate the
# `latest*.yml` files next to the installers — without it nothing updates.
# electron-updater is a production dependency, so it is copied in automatically.
publish:
  - provider: github
    owner: smafnan
    repo: compound
    releaseType: release # never offer a draft or prerelease to users
win:
  target:
    - nsis
  icon: build/icon.ico
nsis:
  oneClick: true
  deleteAppDataOnUninstall: false
  artifactName: Compound-Setup-${version}.${ext}
mac:
  target:
    - dmg
    - zip
  category: public.app-category.productivity
  icon: build/icon.png
  artifactName: Compound-${version}-${arch}.${ext}
  # Ad-hoc sign. Without this electron-builder skips signing entirely and the
  # app ships carrying Electron's own linker signature, which no longer matches
  # the bundle once our asar and icons are inside it. macOS reads a signature
  # that fails to verify as tampering and says "Compound is damaged" — a dead
  # end, with no right-click → Open to get past it. An ad-hoc signature is
  # still unidentified, but it is *valid*, so Gatekeeper falls back to the
  # ordinary "unverified developer" prompt that can be opened through.
  identity: '-'
  # Hardened runtime enforces library validation, which rejects the pre-signed
  # Electron framework under an ad-hoc identity. It only exists to enable
  # notarization, which needs a real certificate anyway.
  hardenedRuntime: false
linux:
  target:
    - AppImage
  icon: build/icon.png
  category: Utility