Skip to content

chore(develop): release 0.16.2 - #234

Merged
jack-arturo merged 1 commit into
developfrom
release-please--branches--develop
Aug 28, 2026
Merged

chore(develop): release 0.16.2#234
jack-arturo merged 1 commit into
developfrom
release-please--branches--develop

Conversation

@jack-arturo

@jack-arturo jack-arturo commented Aug 28, 2026

Copy link
Copy Markdown
Member

🤖 I have created a release beep boop

0.16.2 (2026-08-28)

Bug Fixes

  • backup: page FalkorDB export by node id instead of deep SKIP (#221) (009d58e)
  • config: preserve Ollama defaults and migration checks (0bc0096)
  • docs: complete embedding migration runbooks (3468443)
  • docs: correct re-embedding migration setup (a8be394)
  • enrichment: circuit-break exhausted quota calls (ea148e5)
  • enrichment: circuit-break exhausted quota calls (#229) (ad3ed27)
  • enrichment: preserve quota circuit during in-flight calls (29f359d)
  • mcp-sse: emit the stored date in compact recall output (#224) (42ba8b6)
  • mcp: align the parity harness with its own allowlist (9ac5b4e)
  • mcp: close false-failure and coverage gaps in the parity harness (4cf9ef1)
  • mcp: close partial connections when parity setup fails (89346e9)
  • mcp: isolate parity fixtures per scenario and drop the false alarm (fa458b0)
  • qdrant: index the type payload field so recall filters stop 400ing (c131f02)
  • qdrant: index the type payload field so recall filters stop 400ing (#223) (10bcac7)
  • recovery: honor configured graph and cloud migrations (4dd1325)
  • stream: emit live memory operations on GET /stream (#227) (7a92ebd)

Performance Improvements

  • qdrant: store collection data on disk (#231) (07d8704)
  • qdrant: store new collection data on disk (c97b5b1)
  • qdrant: support disk-backed HNSW restores (b04b9e1)

Documentation

  • add Qdrant on-disk implementation plan (56da2b7)
  • add Qdrant on-disk storage design (e177b60)
  • align provider and maintenance guidance (93afcff)
  • align provider and maintenance guidance (#232) (c40d1d2)
  • enrichment: document quota circuit (d9787cb)
  • mcp: audit remote vs stdio transport parity (92b98ec)
  • qdrant: add on-disk migration runbook (d05a2d9)
  • qdrant: harden on-disk migration runbook (db71f07)
  • qdrant: limit migration to default topology (9b31cde)
  • qdrant: verify migration export before restore (45e77f4)
  • readme: lead benchmark section with neutral AMB numbers (#219) (8ff266e)
  • target feature PRs at develop (#228) (bcef376)

This PR was generated with Release Please. See documentation.

@jack-arturo
jack-arturo merged commit 8987fbd into develop Aug 28, 2026
7 checks passed
@jack-arturo
jack-arturo deleted the release-please--branches--develop branch August 28, 2026 04:32
@jack-arturo jack-arturo mentioned this pull request Aug 28, 2026
Merged
3 tasks
jack-arturo added a commit that referenced this pull request Aug 28, 2026
@jack-arturo
ci(release): pin release-please target-branch to main (#238)
0e8c417 
## Summary
- Pin `release-please-action` to `target-branch: main` so it stops
following the GitHub default branch (`develop`).
- The 0.16.2 attempt opened
[#234](#234) against
develop and closed the real main release PR
[#220](#220). Because
this workflow only runs on `main`, merging #234 never created the
`v0.16.2` tag or GHCR `:stable` images.

## Test plan
- [ ] YAML parses (`python3 -c "import yaml;
yaml.safe_load(open('.github/workflows/release-please.yml'))"`)
- [ ] After merge + promote to `main`, the next Release Please run opens
a PR against `main` (not `develop`)
- [ ] Completing that (or a manual `gh release create v0.16.2`)
publishes the GitHub release and triggers Docker Build for `:stable`
@jack-arturo jack-arturo mentioned this pull request Aug 28, 2026
Merged
4 tasks
jack-arturo added a commit that referenced this pull request Aug 28, 2026
@jack-arturo
chore(release): promote develop to main (#239)
3caa9d5 
## Summary
- Promote `develop` to `main` so 0.16.2 can actually tag.
- Brings the 0.16.2 CHANGELOG from #234 and the Release Please
`target-branch: main` pin from #238.

#220 was closed unmerged after Release Please targeted `develop`. This
promotion is the validated release merge; the GitHub Release / GHCR
`:stable` images follow once `v0.16.2` is tagged.

## Test plan
- [x] #238 CI green (node-test, pre-commit, semantic-pr-title, test
3.10/3.11/3.12)
- [ ] Promote CI green on this PR
- [ ] After merge, `v0.16.2` GitHub Release exists
- [ ] Docker Build publishes `ghcr.io/verygoodplugins/automem:stable`
and `ghcr.io/verygoodplugins/mcp-automem:stable`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

autorelease: pending

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@jack-arturo