Auto-release patch on every green main

[fdmarc]

Summary

• Adds a release job to ci.yml that runs on push to main after the test + dogfood jobs pass
• Computes the next patch from the latest vX.Y.Z tag, creates the tag, force-moves the floating v1, and cuts a GitHub Release via gh release create --latest --generate-notes
• concurrency: release prevents overlapping releases from racing each other
• Merging this PR will produce v1.0.1

Notes

• Marketplace publication is still a one-time manual checkbox per release. Tick it on any published release once to establish/refresh the listing.
• package.json version stays at 1.0.0 (unused at runtime — tags are the source of truth). Can auto-bump it later if drift becomes annoying.

Test plan

• Merge; confirm the release job runs on the resulting main push
• Confirm tag v1.0.1 and updated v1 appear on origin
• Confirm GitHub Release v1.0.1 is created and marked latest

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Implemented automated patch release workflow in CI pipeline that activates on main branch pushes following successful completion of all testing and validation jobs.
  • Automatically computes semantic patch versions, creates and publishes corresponding version tags, and generates GitHub Releases with auto-generated release notes for distribution.

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

Walkthrough

A new automated release job is added to the CI workflow that runs on main branch pushes after test jobs complete. It computes the next semantic patch version by incrementing the latest version tag, creates annotated tags, and publishes a GitHub Release.

Changes

Cohort / File(s)	Summary
CI/CD Release Automation .github/workflows/ci.yml	Added new release job that computes the next patch version from existing git tags (defaulting to v1.0.0), creates and pushes both patch and major version tags, and publishes GitHub Releases with auto-generated notes. Runs conditionally on main branch pushes after test, dogfood-passing, and dogfood-mixed jobs.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐰 With tags and versions dancing right,
The rabbit's CI shines so bright,
Each push to main, a release takes flight,
Patches patch, the versions stack,
Semantic dreams—there's no turning back! ✨

🚥 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 'Auto-release patch on every green main' accurately summarizes the main change—adding an automated release job that creates patch versions whenever tests pass on the main branch.
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
• Commit unit tests in branch auto-release-workflow

---

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