This release adds 3 notable features for engineering teams evaluating rollout.
✓ No known CVEs patched in this version
Summary
AI summaryAdds anomaly detection, a 2‑second grace period, periodic WAL checkpointing, and diagnostic logging to handle SIGTERM/SIGKILL without prior stdin close.
Full changelog
🛡️ SIGTERM Defensive Measures
Protects against MCP clients that violate the spec by sending SIGTERM/SIGKILL without first closing stdin (e.g., OpenCode timeouts, exec.CommandContext cancellation, session crashes).
What's New
- Anomaly detection:
AtomicBooltracks stdin state — logswarn!when SIGTERM arrives without prior stdin close - Grace period: 2-second delay on anomalous SIGTERM allows in-flight operations to complete
- Periodic checkpoint: Storage WAL flush every 5 minutes as insurance against SIGKILL
- Diagnostic logging: Distinguishes normal MCP shutdown from client-side protocol violations
Background
META analysis revealed that OpenCode uses mcp-go library where exec.CommandContext sends os.Kill when context is cancelled (timeout/exit), bypassing the MCP spec shutdown sequence (stdin close → SIGTERM → SIGKILL). Two bugs coexist in the ecosystem:
- Premature kill — hardcoded ~60s MCP timeout kills server mid-operation (opencode#8212)
- Zombie processes — MCP processes not terminated on session end (opencode#6633)
This release adds server-side defenses for scenario #1.
Full Changelog: https://github.com/pomazanbohdan/memory-mcp-1file/compare/v0.2.16...v0.2.17
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About pomazanbohdan/memory-mcp-1file
A self-contained Memory server with single-binary architecture (embedded DB & models, no dependencies). Provides persistent semantic and graph-based memory for AI agents.
Related context
Beta — feedback welcome: [email protected]