Skip to content

Release Notes

Jump to bottom
Bellok edited this page Mar 29, 2026 · 7 revisions

Release Notes

Back to Home

Release history for the Neurodivergent Memory MCP Server. All 0.x releases are research previews.

v0.1.8 — 2026-03-28

Patch release: Forces Docker Hub README refresh on each release and upgrades Node to 24.

Added

  • Added peter-evans/dockerhub-description@v4 step in the release workflow so Docker Hub description is always updated from README.md on every release
  • Added workflow_dispatch to allow manual README refresh runs when needed

Changed

  • Upgraded workflow Node runtime from 20 to 24
  • Upgraded Docker build/runtime base images from node:20-alpine to node:24-alpine

v0.1.7 — 2026-03-28

Patch release: Fixes README GIF and link rendering on Docker Hub and GHCR.

Fixed

  • Replaced relative GIF paths with absolute raw.githubusercontent.com URLs so Docker Hub and GHCR can render the preview image and link correctly

v0.1.6 — 2026-03-28

Patch release: Disables Docker latest tag generation to comply with immutable tag settings.

Fixed

  • Release workflow now sets Docker metadata flavor.latest=false to avoid pushing immutable latest tag
  • Prevents Docker Hub publish failures caused by immutable floating tags

v0.1.5 — 2026-03-28

Patch release: Fixes Docker Hub immutable tag conflict and publishes to the official MCP Registry.

Added

  • Added mcpName field to package.json required for MCP Registry namespace verification (io.github.jmeyer1980/neurodivergent-memory)
  • Added server.json for publishing to the official MCP Registry at registry.modelcontextprotocol.io

v0.1.4 — 2026-03-28

Patch release: Release pipeline hardening and rerun safety.

Fixed

  • Release workflow now syncs release branch with main on version tag pushes
  • Release workflow now skips npm publish when the version already exists on npm (rerun-safe)
  • Continued hardening for GitHub Actions JavaScript runtime migration to Node 24

v0.1.3 — 2026-03-28

First fully successful multi-channel release in this project lifecycle.

What Changed

Improves package visibility in GitHub by publishing container images to GitHub Container Registry (GHCR) in addition to Docker Hub.

Fixed

  • Release workflow now publishes container images to ghcr.io/jmeyer1980/neurodivergent-memory
  • Added packages: write workflow permissions required for GHCR publishing
  • GitHub Packages listing now available through GHCR package pages linked to this repository

v0.1.2 — 2026-03-28

Patch release: Release pipeline reliability and publish resiliency.

Fixed

  • Release workflow now syncs release with main on version tag pushes
  • Release workflow now skips npm publish when the version already exists on npm (rerun-safe)
  • Continued hardening for GitHub Actions JavaScript runtime migration to Node 24

v0.1.1 — 2026-03-28

Initial research preview release.

Added

  • Core MCP Server — knowledge graph storage and retrieval via Model Context Protocol stdio transport
  • 5-District Architecture — semantic organization across logical_analysis, emotional_processing, practical_execution, vigilant_monitoring, and creative_synthesis domains
  • BM25 Full-Text Search — relevance-ranked memory retrieval with configurable scoring and filtering
  • Graph Connections — bidirectional edges between memory nodes for associative traversal
  • Canonical Tag Schema — enforced tagging (topic, scope, kind, layer) for structured knowledge organization
  • Persistence — JSON-based durable storage at .neurodivergent-memory/memories.json
  • Tools: store_memory, retrieve_memory, search_memories, delete_memory, connect_memories, traverse_from, related_to, list_memories, memory_stats, import_memories
  • Docker Support — multi-platform container images (amd64, arm64) with provenance and SBOM attestation
  • Security — npm provenance publishing, container attestation, checksums on release artifacts

Fixed

  • Test script hang prevention — added adaptive timeout and completion detection to prevent indefinite stdin blocking

Known Limitations

  • Single-file persistence — no journal/WAL pattern; risk of data loss on unclean shutdown
  • No concurrency control — unsafe for simultaneous writes from multiple agents
  • Static districts — cannot adapt semantic organization per use case
  • Basic query language — BM25 ranking ignores agent goals or context
  • No observability — no logging, metrics, or debug endpoints
  • No resource controls — unbounded memory growth potential

See also: Architecture · Getting Started · Roadmap

Home

Setup

Reference

Reports

v0.3.0 · Research Preview

npm · Docker Hub · GHCR

Clone this wiki locally