Skip to content

Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors

Rust

docs(agents): make updating the Homebrew tap a mandatory release step

AkitaOnRailsf79dbb7b584f
diff --git a/AGENTS.md b/AGENTS.md
index 1bebc691..65ab7ac2 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -494,6 +494,16 @@ Additional boundary rules:
release**: dispatch `ci` (macOS legs) and `windows` on the exact
release-candidate SHA and wait for green before tagging. Never tag a
release whose SHA lacks a green full matrix.
+- **Every release updates the Homebrew tap — do not forget it.** After
+ `release.yml` publishes the GitHub release and its per-target tarballs,
+ update `~/Projects/homebrew-tap/Formula/ai-memory.rb`: bump `version` and
+ set each platform `sha256` to the value from the release's published
+ `ai-memory-<target>.tar.gz.sha256` assets (`macos-aarch64`, `macos-x86_64`,
+ `linux-aarch64`, `linux-x86_64`), then commit (`ai-memory X.Y.Z`) and push
+ the tap. Verify each `sha256` matches the published asset before pushing — a
+ wrong hash makes `brew install` fail for everyone. This is a mandatory,
+ recurring post-release step (it has been forgotten repeatedly); do not rely
+ on a contributor PR to the tap to remember it.
- **No version bumps or release tags without explicit user approval.**
Do not bump crate/package versions automatically.
- **PR evaluation:** report pros, cons, and recommended fix, then ask for