Windows release artifacts are currently confusing.
Current issue:
- release may contain both ambiguous win-x64.exe and named Setup/Portable artifacts
- users cannot easily tell what to download
- portable exe and zip duplicate the same use case
Target artifact set:
- Windows installer: Zap-Browser-Setup-${version}-x64.exe
- Windows portable: Zap-Browser-Portable-${version}-x64.zip
- Linux AppImage
- Linux deb
- Linux rpm
Goals:
- remove standalone portable exe target
- keep only NSIS installer and portable zip for Windows
- use deterministic artifact names
- prevent stale assets from previous release rebuilds
Windows release artifacts are currently confusing.
Current issue:
Target artifact set:
Goals: