Remove beta release workflow

[sestinj]

Summary

• Delete beta-release.yml — no longer used
• Simplify stable-release.yml — remove promote-beta path, make stable_version the only required input, remove all beta-related steps and conditionals

Test plan

• Trigger stable release workflow with a version and confirm it works

🤖 Generated with Claude Code

---

Continue Tasks: ✅ 7 no changes — View all

---

Summary by cubic

Removes the beta release workflow and simplifies the stable release to a single, versioned path. This reduces maintenance and makes releases faster and clearer.

• Refactors

  • Delete .github/workflows/beta-release.yml.
  • Simplify .github/workflows/stable-release.yml to require only inputs.stable_version.
  • Remove beta promotion logic, conditionals, and verification steps.
  • Consolidate publish and release steps; tags and GitHub releases use the provided version.
  • Blueprint publishing retained and now references inputs.stable_version.

• Migration

  • Trigger the Stable Release workflow with stable_version (e.g., 1.2.3).
  • Ensure SEMANTIC_RELEASE_TOKEN and RUNLOOP_API_KEY secrets are set.

^{Written for commit dfdbeda. Summary will update on new commits.}

[continue]

Documentation Review: No docs updates needed.

This PR removes an internal CI/CD workflow (beta-release.yml) and simplifies the stable release workflow. These are maintainer-facing changes to release automation, not user-facing changes.

The existing CLI documentation correctly points users to install @continuedev/cli without referencing internal release channels. Users don't need to know about the beta/stable workflow distinction—they simply install the latest published version.

No changes to developer understanding or usage patterns result from this PR.

[cubic-dev-ai]

No issues found across 2 files