ci(v3): attach artifacts to nightly releases

[leaanthony]

Summary

• explicitly dispatch Release v3 after the nightly release task creates a tag
• carry the tagged beta through the existing multi-platform binary, checksum, and provenance workflow
• surface the hand-off in the nightly summary

Fixes #5876

Why

The nightly workflow uses GITHUB_TOKEN to create tags. GitHub intentionally does not trigger a second workflow from those tag pushes, so beta.2 received a GitHub release with no downloadable desktop artifacts.

Validation

• YAML parsed successfully
• git diff --check
• actionlint .github/workflows/nightly-release-v3.yml reports only pre-existing diagnostics (the actions/setup-go@v4 version and existing shellcheck style warnings); the new dispatch block has no actionlint finding.

The dispatched Release v3 workflow remains the single publisher of binaries, SHA256SUMS, and provenance.

Summary by CodeRabbit

• New Features
  • Successful non-dry-run releases now automatically trigger desktop artifact builds and attachment.
  • Release tags, prerelease status, and draft settings are carried into the artifact workflow.
  • Release summaries now indicate when the artifact build is dispatched.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 84fea70d-6364-4e69-86f6-b5f8fbda559c

📥 Commits

Reviewing files that changed from the base of the PR and between 733757c and fac63f2.

📒 Files selected for processing (1)

• .github/workflows/nightly-release-v3.yml

---

Walkthrough

The nightly v3 release workflow now dispatches release-v3.yml after successful non-dry-run releases. It passes the release tag, prerelease status, and draft setting, then records the dispatch in the workflow summary.

Changes

Release artifact dispatch

Layer / File(s)	Summary
Post-release artifact dispatch .github/workflows/nightly-release-v3.yml	The workflow dispatches release-v3.yml with release metadata after a successful live release and reports the dispatch in the release summary.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• wailsapp/wails#5318: Adds the release-v3.yml workflow that this change dispatches.
• wailsapp/wails#5665: Modifies the same nightly v3 release workflow.
• wailsapp/wails#5815: Modifies the release-v3.yml workflow inputs used by this dispatch.

Suggested labels: reviewed ✅

Suggested reviewers: taliesin-ai

Poem

I’m a rabbit with a release tag bright,
Dispatching desktop artifacts into flight.
Beta flags hop, drafts stay away,
The summary records the workflow’s day.
Thump, thump—artifacts lead the way!

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch agent/beta3-release-artifacts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[Copilot]

Pull request overview

This PR updates the v3 nightly release workflow to explicitly dispatch the existing Release v3 workflow after a nightly tag is created, ensuring each nightly GitHub release receives the full set of desktop binaries, checksums, and provenance artifacts.

Changes:

• Add an explicit gh workflow run release-v3.yml dispatch step after successful nightly tagging.
• Pass the created tag and derived pre_release flag into the Release v3 workflow inputs.
• Surface the hand-off status in the nightly workflow step summary.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.