Release checklist
HISE Release Checklist
Review the actual package variant and exported binary, not only the authoring overlay.
SoundSync
Release checks
| Area | Exercise |
|---|---|
| Product and environment | Correct saved product, credential scope, package variant/version, and intended API environment |
| Installation | Correct script include or native sources, verified source patch, rebuilt HISE, and exported project integration |
| Fresh customer | Valid serial/account path, owner proof, email verification, and successful activation |
| Invalid customer | Unknown serial, owner mismatch, missing entitlement, and existing-account recovery |
| Devices | Device limit, old-device deactivation, changed machine, and reactivation |
| Network and cache | Cold start, permitted prior-valid grace, expired grace, invalid cache, and restored connectivity |
| Enforcement | Protected audio/features lock in the final exported plugin, including editor-closed native use |
| Recurring access | Renewal, failure/grace, cancellation, expiration, and refund policy for the selected product |
| Customer surfaces | Store, My Products, downloads, support links, and customer-session expiry |
| Branding and release | Logo/colors, regeneration, actual host/format/OS, and no private data in public media |
Keep evidence with the build
Record the exact binary/package version and test environment. Source tracing, package-generation tests, a screenshot, and a runtime access test establish different things. Do not call every row passed because another product or package variant passed it.
Never run native source-patch tools against a production build checkout without understanding the targeted paths and retaining your own recoverable configuration.