Open source Grok Bot alternative, Bring your own agent and subscription: message Claude Code, Codex, Gemini CLI, Cursor, Copilot and 40+ AI agents as bots on your own computer, from iPhone, Mac, Windows, Linux or terminal. Agent-agnostic and free. Also a Muse and Dots alternative. Built in Rust.
Rust acpagent-client-protocolai-agentsai-assistantclaudeclaude-codecodexcoding-agentscursorgeminigemini-cligrok-bot-alternativeiosiphonelinuxmacosmcpopen-sourcerustself-hosted
ci: post each new release to the Discord #releases channel
leepokaib638c48eb5c9
diff --git a/.github/workflows/auto-tag.yml b/.github/workflows/auto-tag.ymlindex 01a9100f..5d99c206 100644--- a/.github/workflows/auto-tag.yml+++ b/.github/workflows/auto-tag.yml@@ -29,6 +29,7 @@ jobs:- name: Create tag and release if not existsenv:GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}+ DISCORD_RELEASES_WEBHOOK: ${{ secrets.DISCORD_RELEASES_WEBHOOK }}run: |TAG="v${{ steps.version.outputs.version }}"if git rev-parse "$TAG" >/dev/null 2>&1; then@@ -40,4 +41,11 @@ jobs:# Created here, before the build jobs upload to it, so it carries a description.tools/release-notes.sh "$TAG" > notes.mdgh release create "$TAG" --verify-tag --title "$TAG" --notes-file notes.md --generate-notes+ # Announce it in the Discord server's #releases channel. A release created with+ # GITHUB_TOKEN triggers no `release` workflow, so this happens here.+ jq -n --arg tag "$TAG" --arg url "https://github.com/$GITHUB_REPOSITORY/releases/tag/$TAG" --rawfile notes notes.md \+ '{embeds: [{title: "Codync \($tag)", url: $url, color: 16777215,+ description: (if ($notes | test("\\S")) then $notes[0:4000] else "See the release notes." end)}]}' |+ curl -fsS -X POST -H "Content-Type: application/json" --data @- "$DISCORD_RELEASES_WEBHOOK" ||+ echo "::warning::Couldn't post $TAG to Discord"fidiff --git a/docs/guides/development.md b/docs/guides/development.mdindex c26077cb..a1a8263f 100644--- a/docs/guides/development.md+++ b/docs/guides/development.md@@ -103,7 +103,7 @@ Versions are defined in `apps/project.yml` (`MARKETING_VERSION`), `host/Cargo.to## GitHub releases-Auto Tag (`.github/workflows/auto-tag.yml`) creates each `v*` release right after pushing the tag, before the host and desktop jobs upload to it. Its description comes from `tools/release-notes.sh`: the `## Summary` of the PR that merged the version bump into `main` (or the PR's opening text without that heading), else the `feat`/`fix` commits since the previous tag, followed by GitHub's generated PR list and compare link. Write the release PR's Summary for people reading the release page.+Auto Tag (`.github/workflows/auto-tag.yml`) creates each `v*` release right after pushing the tag, before the host and desktop jobs upload to it. Its description comes from `tools/release-notes.sh`: the `## Summary` of the PR that merged the version bump into `main` (or the PR's opening text without that heading), else the `feat`/`fix` commits since the previous tag, followed by GitHub's generated PR list and compare link. Write the release PR's Summary for people reading the release page. The same description is posted to the Discord server's #releases channel through the webhook in the `DISCORD_RELEASES_WEBHOOK` secret (a failed post only leaves a warning on the run).## iOS releases (Xcode Cloud)