release: v0.3.0-beta.2

[gnanirahulnutakki]

Corrected beta release boundary

Promotes the draft-safe beta publication fix from dev to main for a new immutable v0.3.0-beta.2 tag.

• beta.1 remains an untouched unpublished draft after its workflow safely failed at draft tag lookup
• fix(e9): publish beta drafts by release ID #160 replaces the draft-invisible REST tag endpoint with gh release view --json databaseId
• beta publication remains prerelease=true and API string make_latest=false; stable release behavior is unchanged

Evidence

• exact post-merge dev CI: 29368327885 passed
• exact post-merge dev CodeQL: 29368327085 passed
• beta.1 tag was GitHub-verified; its generated artifacts, signatures, and attestations remain only in an unpublished draft

After this PR is independently green and merges, the exact main CI will run before creating a new signed v0.3.0-beta.2 tag.

Summary by CodeRabbit

• Bug Fixes

  • Improved beta release publishing so draft releases are correctly identified and published as prereleases without affecting the latest stable release.

• Tests

  • Added validation to ensure beta releases use database-ID-based draft resolution and avoid tag-based lookup errors.

• Documentation

  • Added incident notes, verification criteria, and testing guidance for the beta release publication workflow.

[coderabbitai]

📝 Walkthrough

Walkthrough

The beta release workflow now obtains the release database ID with gh release view, preserving the existing publication PATCH behavior. A policy test enforces this lookup, and a session document records the repair plan and completion criteria.

Changes

Beta release publication repair

Layer / File(s)	Summary
Beta release lookup and validation .github/workflows/release.yml, tests/scripts/release_tag_policy_test.sh, sessions/2026-07-14-e9-beta-draft-publish.md	The beta path resolves release_id through gh release view --json databaseId; the policy test rejects tag-endpoint lookup and the session record documents the repair plan and verification criteria.

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

Possibly related issues

• P0 E9: publish beta draft release by database ID #159 — Directly covers the database-ID draft-release lookup and corresponding policy-test changes.
• P1 E9: publish signed macOS-arm64 beta prereleases without replacing latest stable #154 — Covers beta prerelease publication while preserving the latest stable release.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title is related to the PR because it identifies the beta release tag being promoted, though it does not describe the workflow fix itself.
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.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch dev

---

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@tests/scripts/release_tag_policy_test.sh`:
- Line 53: Strengthen the assertion in the release workflow validation around
the grep for `gh release view` so it verifies scalar extraction via `--jq
'.databaseId'`, not just the `--json databaseId` field. Match the complete
command or add a separate assertion covering the jq expression.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: cbb22021-5c99-49d4-8e9c-4945cd1aa33c

📥 Commits

Reviewing files that changed from the base of the PR and between 5fe4008 and ad0a819.

📒 Files selected for processing (3)

• .github/workflows/release.yml
• sessions/2026-07-14-e9-beta-draft-publish.md
• tests/scripts/release_tag_policy_test.sh

[coderabbitai]

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Assert scalar database ID extraction.

Line 53 checks only --json databaseId; it would still pass if --jq '.databaseId' were removed and the full JSON object were passed to the PATCH URL. Match the complete lookup or separately assert the --jq expression.

🧰 Tools

🪛 Shellcheck (0.11.0)

[info] 53-53: Expressions don't expand in single quotes, use double quotes for that.

(SC2016)

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@tests/scripts/release_tag_policy_test.sh` at line 53, Strengthen the
assertion in the release workflow validation around the grep for `gh release
view` so it verifies scalar extraction via `--jq '.databaseId'`, not just the
`--json databaseId` field. Match the complete command or add a separate
assertion covering the jq expression.