Release notes

## Release practice Every release should include a version, release date, customer impact and rollback note. Describe fixed issues and security changes clearly without disclosing exploitable details. ## Customer communication Publish product release notes alongside the updated asset so entitled customers can see what changed before downloading. For service-impacting changes, use a customer notice and support process in addition to the normal release note. ## Verification Before publishing, verify the asset upload, protected-package result where applicable, payment entitlement, signed download and customer-facing documentation in a test account.