Fix repository targeting and preview release publication

[Telli]

The release publish job downloads artifacts without checking out the repository, so GitHub CLI cannot infer the target repository. Set GH_REPO explicitly and mark preview version tags as prereleases instead of stable releases.

Add a clear error for a missing NuGet publishing key and document credential setup and rerunning the same tagged workflow after configuration.

Validation: actionlint 1.7.12 passes for CI and release workflows; git diff --check passes. The existing build, package installation, documentation, and native smoke gates remain required.

Summary by CodeRabbit

• Release Management

  • Versions containing a prerelease label are now published as GitHub prereleases and won’t be marked as the latest release.
  • Stable versions continue to be published as standard GitHub releases.
  • NuGet publishing now reports an explicit error when the required publishing key is missing.

• Documentation

  • Added guidance for configuring the publishing key and rerunning failed tagged releases while retaining validated artifacts.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 4809b490-2302-469f-9cfe-528edd9c13b9

📥 Commits

Reviewing files that changed from the base of the PR and between fd04d57 and 025e0af.

📒 Files selected for processing: 2

• .github/workflows/release.yml
• docs/binary-distribution.md

Included review availability: This review used your included allowance. Your plan provides up to 2 included reviews per hour; 1 remain after this review.

📝 Walkthrough

The release workflow now checks for a NuGet API key before publishing packages and creates GitHub prereleases for versions that contain a hyphen. The distribution documentation explains the secret setup, missing-key failure, reruns, and prerelease tags.

Changes: Release workflow

Layer / File(s)	Summary
Publishing and release behavior .github/workflows/release.yml, docs/binary-distribution.md	The workflow stops NuGet publishing when NUGET_API_KEY is empty. It sets the repository and validated version for GitHub release creation, and adds prerelease flags when the version contains a hyphen. The documentation describes secret setup, rerunning failed jobs on the same tag, and prerelease tags.

Priority: ➖ Normal

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

Change: Bug fix

Merge Risk: ⚪ Minimal · up to 025e0

The release workflow validates artifacts before publishing, stops when the NuGet key is missing, and marks documented hyphenated preview tags as prereleases. No actionable merge-blocking risk was established.

Pre-merge checks: 5

Check name	Status	Explanation
Description check		The description explains the release publishing changes and reports validation results. It does not include the required "Risk and compatibility" section or its checklist items, but the main required …
Title check		The title clearly describes the main changes: explicit repository targeting and prerelease publication for preview versions.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.}