Skip to content

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.

docs: codync-mem and codync-network only publish through the workflow

leepokaiba11423aed8b
diff --git a/docs/guides/development.md b/docs/guides/development.md
index 6eafb6e1..57fd5514 100644
--- a/docs/guides/development.md
+++ b/docs/guides/development.md
@@ -160,7 +160,7 @@ Auto Tag (`.github/workflows/auto-tag.yml`) creates each `v*` release right afte
The memory crate (`host/crates/memory`) has its own 0.x version and ships with the Codync release that carries its changes, through `.github/workflows/memory-crate.yml`:
- A pull request into `main` that changes the crate (its `.github`, the mirror's CI, aside) fails unless the crate's `version` differs from `main`'s.
-- The push to `main` mirrors the crate to [leepokai/codync-mem](https://github.com/leepokai/codync-mem) (write deploy key in the `CODYNC_MEM_DEPLOY_KEY` secret), then publishes its version to crates.io unless crates.io already has it. Publishing uses trusted publishing: the crate's Settings → Trusted Publishing on crates.io trusts `leepokai/Codync` with the workflow `memory-crate.yml`, so no token is stored.
+- The push to `main` mirrors the crate to [leepokai/codync-mem](https://github.com/leepokai/codync-mem) (write deploy key in the `CODYNC_MEM_DEPLOY_KEY` secret), then publishes its version to crates.io unless crates.io already has it. Publishing uses trusted publishing: the crate's Settings → Trusted Publishing on crates.io trusts `leepokai/Codync` with the workflow `memory-crate.yml`, so no token is stored. Both crates also have **Require trusted publishing** on (since 2026-10-26): crates.io refuses a version published with an API token, so a release goes through the workflow or not at all.
To bump, set `version` in `host/crates/memory/Cargo.toml` (patch for fixes, minor for API changes while 0.x) and run `cargo check -p codync-mem` in `host/` to update its `Cargo.lock` entry. A published version can't be deleted, only yanked.