ci: publish nightly on demand only

[shivamhwp]

The Nightly workflow triggered on every push to main:

on:
  push:
    branches:
      - main
  workflow_dispatch:

Its publish step is not passive — it force-moves the nightly tag and clobbers the rolling release's assets:

git tag -f nightly "$COMMIT_SHA"
git push origin refs/tags/nightly --force
gh release upload nightly "${assets[@]}" --clobber

So every commit to main shipped straight to early-access users with no decision point. Publishing a nightly is a release decision; it shouldn't be a side effect of a push.

This drops the push trigger, leaving workflow_dispatch only. Trigger deliberately:

gh workflow run Nightly            # main's tip
gh workflow run Nightly --ref <ref>   # or any other ref

No change to the build or publish logic itself.

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
wrec	Ready	Preview	Jul 29, 2026 11:01pm

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[greptile-apps]

Greptile Summary

This PR makes nightly releases explicitly on-demand.

• Removes the push trigger for main.
• Retains manual workflow_dispatch execution.
• Documents why publishing must be deliberately triggered.

Confidence Score: 5/5

The PR appears safe to merge with no actionable issues identified.

The workflow remains manually dispatchable, and the build and publication logic is unchanged; only the unintended automatic trigger is removed.

Important Files Changed

Filename	Overview
.github/workflows/nightly.yml	Removes automatic nightly publication on main pushes while preserving the existing manual build and release workflow.

_{Reviews (1): Last reviewed commit: "ci: publish nightly on demand only" | Re-trigger Greptile}