ci: stop nightly alpha tags for release 0.3

[willkill07]

Overview

Remove release/0.3 from the nightly alpha tag branch list now that the release line no longer needs nightly tags.

• I confirm this contribution is my own work, or I have the right to submit it under this project's license.
• I searched existing issues and open pull requests, and this does not duplicate existing work.

Details

• Removed release/0.3 from .github/nightly-alpha-branches.yaml.
• Left main as the only branch configured for nightly alpha tags.

Where should the reviewer start?

.github/nightly-alpha-branches.yaml

Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

• Relates to: none

Summary by CodeRabbit

• Chores
  • Updated nightly build configuration to consolidate releases and focus on the main development branch.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Enterprise

Run ID: 98fd3f30-a102-4cff-80a3-2682c0ea9d03

📥 Commits

Reviewing files that changed from the base of the PR and between bb18d99 and 8c109e8.

📒 Files selected for processing (1)

• .github/nightly-alpha-branches.yaml

💤 Files with no reviewable changes (1)

• .github/nightly-alpha-branches.yaml

---

Walkthrough

The nightly alpha CI configuration was simplified to build only the main branch by removing the release/0.3 branch entry. This reflects a change in which branches receive nightly alpha builds.

Changes

Nightly CI Configuration

Layer / File(s)	Summary
Remove release/0.3 from nightly builds .github/nightly-alpha-branches.yaml	The branches: list in the nightly alpha workflow was updated to exclude release/0.3, retaining only main for nightly alpha builds.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title follows Conventional Commits format with type 'ci', clear imperative summary, is under 72 characters, and directly describes the configuration change.
Description check	✅ Passed	The description includes all required sections with substantive content: Overview explaining the rationale, Details listing specific changes, reviewer start point, and confirmation checkboxes marked complete.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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