an open-source alternative to the dots, bots and muses of the world, run an office of claude code/codex like agents on your laptop, sandboxes or anywhere, uses your existing subscriptions
HTML agent-harnessagent-orchestrationagentsai-agentsautonomous-agentsclaude-codecodexcoding-agentsdesktop-appdeveloper-toolselectrongemini-cliharnessharness-engineeringlocal-firstmemorymulti-agentopencodeorchestrationtypescript
ci(release): publish suffixed tags as pre-releases
Chaitanya Giricda93a5e6b2b
diff --git a/.github/workflows/release.yml b/.github/workflows/release.ymlindex 3a892dc7..9eb1b5a4 100644--- a/.github/workflows/release.yml+++ b/.github/workflows/release.yml@@ -132,6 +132,15 @@ jobs:with:# RELEASE.md is the human-facing notes; GitHub shows it as the body.body_path: RELEASE.md+ # A tag carrying a pre-release suffix (v0.4.4-rc.1, -beta.2 …) publishes+ # as a PRE-RELEASE. This is load-bearing, not cosmetic: the in-app+ # updater polls /releases/latest, and GitHub excludes pre-releases from+ # that endpoint. So an rc gets a real, public, shareable download page+ # WITHOUT offering itself to every installed copy of the app — which is+ # exactly what you want for a build that needs testing on a platform the+ # authors cannot run. A clean `vX.Y.Z` tag is unaffected and still ships+ # as the latest release to everyone.+ prerelease: ${{ contains(github.ref_name, '-') }}fail_on_unmatched_files: falsefiles: |release/*.dmg