docs(release): clarify desktop asset availability

[txhno]

Fixes #611.

This updates the desktop release body and release guide so they no longer imply installers are always attached. The release messaging now tells users to download attached assets when present and points them to the deploy templates otherwise.

Validation:

• reviewed the final diff for the workflow and release guide changes
• parsed .github/workflows/desktop-release.yml with yaml.safe_load

---

Note

Low Risk
Low risk documentation/workflow copy change only; it updates GitHub Release body text and the release guide without altering build or publishing behavior.

Overview
Updates the desktop release workflow’s GitHub Release body (stable + nightly) to say installers should be downloaded from attached assets only when the desktop upload succeeds, and adds guidance to use deploy/ templates when no assets are present.

Adjusts RELEASE.md to reflect the same expectation: desktop artifacts appear after the desktop workflow completes successfully, and release communications should redirect users to deploy/ if installers aren’t attached yet.

^{Reviewed by Cursor Bugbot for commit d5b344d. Bugbot is set up for automated code reviews on this repo. Configure here.}

[ital0]

Hi @txhno :)

Sorry for the long wait on this.

The underlying issue is valid: release copy shouldn't imply installers exist when assets didn't upload. We can't merge this version though. The branch conflicts with main, and the desktop-release.yml hunks no longer apply (release copy moved to other files since this was opened). The deploy/ fallback also isn't the right path for desktop installers; that folder is for self-hosted server deployments.

If you want to take another pass later with a rebase, happy to review again.

Thanks for the contribution.

[github-actions]

Preview environment destroyed 🧹

Stack preview-pr-720 and its Cloudflare subdomain have been cleaned up.