Fixed
- CI now rejects a change that writes into an already-released CHANGELOG
section.bin/releaserenames## [Unreleased]to## [X.Y.Z], so a branch
opened before a release carries a diff anchored at the old line numbers and
git merges it into whatever section now occupies them — silently, with no
conflict. Three entries landed in the wrong release this way (#491 into
1.32.0, #502 into 1.32.2, #517 into 1.33.0), each claiming a fix shipped in a
version that did not contain it while the version that did listed nothing.
scripts/check-changelog-frozen.shcompares a branch against its merge base
and fails on any touched line below[Unreleased]. - The
ingest (server, this process)counters inai-memory statusnow move
for events delivered overPOST /hook/batch. They were instrumented only in
the per-eventPOST /hookhandler, while the spool drain posts batches and
falls back to/hookonly against a pre-upgrade server, so a current client
against a current server left the whole section readingaccepted 0,
last write: -and zero sheds while observations were landing normally — the
section exists precisely to tell "hooks are not arriving" apart from "hooks
are arriving but nothing is stored", and it reported the same thing for both.
A batch 429 also now counts every item it rejects, not just the one that
found no permit, so shed volume is comparable between the two routes instead
of understated by up to the batch size (#516). last writein the same section now advances only when an event actually
cleared the writer.handle_hookstamped it unconditionally after processing
returned, and processing swallows its errors, so a store rejecting every
event — read-only database, exhausted disk, a failed migration — still
reported a fresh write time and looked healthy (#516).
Checksums (SHA256)
9df8b298a0d9034fc4469205807c069c363a8e9954dd4afe5c1e95afd1cf6abc ai-memory-hooks.tar.gz
448f6cfad616e13692598dd49709ce9dec10eed0f702818ccca4a0c54a79f8c7 ai-memory-install-hooks
77b956b0f8d6e4be4b4e75b5a2c1548a7e4e218c9a1515d04be33268e0782d1f ai-memory-linux-aarch64.tar.gz
777645c3e3103bb9fb64eb50b7cf92e1a962f8f091e28d3bb4cb526ec2f741b1 ai-memory-linux-x86_64.tar.gz
0459b85964306342109b5d9ea6f954b9d9126cc46f7347133ede6797a333d10b ai-memory-macos-aarch64.tar.gz
4d15ad28807c8545682afe18e332720e4cd41ab32ceb05c7ca1784550d79d132 ai-memory-macos-x86_64.tar.gz
8b692f8086dde578b25a4a7c6d1373e4f25bd366a950310f4fb03d5e3f8617f0 ai-memory-windows-x86_64.zip
6a91c44ffa2e85d3b5a6ce26a4ccff0286b91d08d276d2bb4d47c346b036ee8b ai-memory-wrapper.cmd
780415c858edb6dc1e0da5066081cb840566ffa74ddb6b1d613c837541916b97 ai-memory-wrapper.ps1
52afdf14994ae9b4eb3dcfc09f1d5b12a47b8936d2f0ca14fdf03997565bc545 ai-memory-wrapper
Install
# Arch Linux (AUR)
yay -S ai-memory-bin # prebuilt Linux x86_64/aarch64 binary
yay -S ai-memory # builds from source
# Docker
docker pull akitaonrails/ai-memory:1.33.1
# macOS aarch64/x86_64 (no toolchain): download the matching ai-memory-macos-<arch>.tar.gz below,
# extract it, and follow the bundled docs/macos.md.
# Windows x86_64 (no toolchain): download ai-memory-windows-x86_64.zip below,
# extract it, and follow the bundled docs/windows.md.
# From source
cargo install --git https://github.com/akitaonrails/ai-memory --tag v1.33.1