Release process

Publish every Saleculator release the same way.

This is the operational checklist for future releases on saleculator.com so customers, vendors, and support assistants always know what to download and verify.

Package names

The final Windows installer should use a clear versioned name such as Saleculator-4.5.1-Setup.exe. The vendor package should use a matching versioned ZIP such as saleculator-4.5.1-runtime.zip.

Application JAR

The final application JAR inside the release package should be named Saleculator.jar and should be obfuscated for public release builds.

Release location

Each public release gets its own folder under /releases/<version>/ with downloads, release notes, and SHA256SUMS.txt.

Windows signing

Public Windows installers should be Authenticode-signed before customer publication. Keep certificate paths and passwords in release-machine environment variables, not in source control or release packages.

Release metadata

Publish /releases/latest.json, /downloads/latest.json, and /releases/<version>/release.json so installers, support tools, and AI assistants can discover the current package and verify checksums.

Updater metadata

Modern clients read /releases/version.html. Older clients may still read /update/version.html. Both must use the bracketed token format expected by the POS updater.

Before upload

Build quality gate

Build the installer and runtime ZIP from the same source release.
Confirm the JAR is named Saleculator.jar inside the package.
Confirm the release JAR is obfuscated.
Run npm run verify-release before deployment.
For public Windows releases, sign the installer and run npm run verify-release:signed on a Windows validation machine.
Run Windows install, Linux runtime, and MySQL setup smoke tests.
Verify trial request, activation, PIN login, sample bill, receipt print, backup, and support-info output.
Generate SHA-256 hashes for every public downloadable file.

After upload

Public validation gate

Confirm installer and ZIP download URLs return HTTP 200.
Confirm SHA256SUMS.txt matches the uploaded files.
Confirm /releases/latest.json, /downloads/latest.json, and version release.json match the uploaded files.
Confirm the release page contains customer-friendly release notes and upgrade precautions.
Confirm /releases/version.html has the new updater token.
Run npm run verify-release:public after deployment.
Confirm preserved legacy files under /update/ still work.
Run the production health monitor or inspect /var/log/saleculator-site-health.log after deployment.