doobidoo/mcp-memory-service v10.69.0

v10.69.0 — mistake_note_update/delete + Docker multi-arch fix + log-injection CI guard

on GitHub

What's New

Added

• feat(mistake_notes): mistake_note_update and mistake_note_delete MCP tools (closes #1035, PR #1045, @filhocf): Two new tools extend the Mistake Notes system. mistake_note_update lets you patch failure_count or content on an existing note by content_hash. mistake_note_delete removes a note by content_hash. Both validate memory_type='mistake' before operating to prevent accidental mutations on non-mistake memories.

Fixed

• fix(ci): disable buildx provenance/sbom attestations in publish-docker job (fixes #1044): docker/build-push-action v4+ pushes provenance and SBOM attestation manifests to the registry by default. On ghcr.io, the multi-arch index ended up referencing these attestation entries instead of the actual platform layers, so docker pull ghcr.io/doobidoo/mcp-memory-service:latest hit a manifest unknown error. Fixed by setting provenance: false and sbom: false in the publish-docker job.

Changed

• chore(ci): log-injection guard in pre_pr_check.sh (check 6.5): pre_pr_check.sh now scans for f-string logger calls missing _sanitize_log_value() wrapping — catches py/log-injection patterns locally before CodeQL runs. CLAUDE.md updated with a Log Injection Guard section documenting the pattern.

Special Thanks

Huge thanks to @filhocf for continued contributions — the mistake_note_update and mistake_note_delete tools (PR #1045) round out the Mistake Notes CRUD surface.

Full Changelog

See CHANGELOG.md for the complete entry.