memory-journal-mcp 6.1.2 → 6.2.1

package/releases/v3.1.0.md

@@ -1,104 +0,0 @@
-# v3.1.0 - GitHub Projects v2 Kanban Support
-
-**Release Date:** January 11, 2026
-
-## Highlights
-
-This release adds GitHub Projects v2 Kanban board integration, comprehensive AI agent instructions, and infrastructure updates including a Docker Node.js upgrade and dependency updates.
-
----
-
-## Added
-
-### GitHub Projects v2 Kanban Support
-
-View and manage GitHub Project boards directly from AI agents:
-
-- **New Tool: `get_kanban_board`** — Fetch project items grouped by Status columns (Backlog, Ready, In progress, In review, Done)
-- **New Tool: `move_kanban_item`** — Move items between status columns using GraphQL mutations
-- **New Resource: `memory://kanban/{project_number}`** — JSON board data with items grouped by status
-- **New Resource: `memory://kanban/{project_number}/diagram`** — Mermaid visualization of Kanban board
-- **Multi-level project discovery** — Searches user → repository → organization level projects automatically
-- **Dynamic status columns** — Supports any Status field configuration per project
-
-### Server Instructions
-
-Usage instructions are now automatically provided to AI agents via the MCP protocol's `instructions` capability during server initialization.
-
-- Explicit MCP access patterns (`CallMcpTool`, `ListMcpResources`, `FetchMcpResource`)
-- Tool parameter reference tables for all 29 tools
-- Default GitHub Projects v2 status column documentation
-- Guidance for finding correct project by `projectTitle`
-
-See [`src/constants/ServerInstructions.ts`](https://github.com/neverinfamous/memory-journal-mcp/blob/main/src/constants/ServerInstructions.ts)
-
----
-
-## Fixed
-
-### Dependabot Configuration
-
-Migrated from deprecated `pip` ecosystem to `npm` ecosystem:
-
-- **Root Cause**: The v3.0.0 TypeScript rewrite removed all Python dependency files, but Dependabot was still configured for `pip`
-- **Symptom**: Dependabot security scans failed with `dependency_file_not_found: / not found`
-- **Resolution**: Replaced `pip` ecosystem with `npm` ecosystem and updated dependency groups to match TypeScript/Node.js packages (MCP SDK, Zod, sql.js, vectra, build tools, linting)
-
----
-
-## Changed
-
-### Docker Base Image
-
-Upgraded from `node:22-alpine` to `node:24-alpine` (Active LTS):
-
-- Node.js 24 is the current Active LTS release (support through April 2028)
-- Node.js 25 was skipped as it's a non-LTS "Current" release (EOL June 2026)
-
-### Dependency Updates
-
-| Package                     | Previous | New    | Type  |
-| --------------------------- | -------- | ------ | ----- |
-| `@modelcontextprotocol/sdk` | 1.25.1   | 1.25.2 | patch |
-| `@octokit/rest`             | 21.1.1   | 22.0.1 | major |
-| `globals`                   | 16.5.0   | 17.0.0 | major |
-| `typescript-eslint`         | 8.50.1   | 8.52.0 | minor |
-| `vectra`                    | 0.9.0    | 0.11.1 | minor |
-| `zod`                       | 4.2.1    | 4.3.5  | minor |
-
-**Note:** Updated `vectra` `queryItems` call to new API signature with BM25 hybrid search support.
-
----
-
-## Capabilities Summary
-
-| Category        | Count | Notes                                                                 |
-| --------------- | ----- | --------------------------------------------------------------------- |
-| **Tools**       | 29    | +2 Kanban tools (`get_kanban_board`, `move_kanban_item`)              |
-| **Tool Groups** | 8     | core, search, analytics, relationships, export, admin, github, backup |
-| **Prompts**     | 14    | Unchanged from v3.0.0                                                 |
-| **Resources**   | 16    | +2 Kanban resources                                                   |
-
----
-
-## Installation
-
-**npm:**
-
-```bash
-npm install -g memory-journal-mcp@3.1.0
-```
-
-**Docker:**
-
-```bash
-docker pull writenotenow/memory-journal-mcp:3.1.0
-```
-
----
-
-## Links
-
-- [Full Changelog](https://github.com/neverinfamous/memory-journal-mcp/wiki/CHANGELOG)
-- [GitHub Repository](https://github.com/neverinfamous/memory-journal-mcp)
-- [Documentation Wiki](https://github.com/neverinfamous/memory-journal-mcp/wiki)

package/releases/v3.1.1.md

@@ -1,42 +0,0 @@
-# v3.1.1 - Security Patch
-
-**Release Date:** January 11, 2026
-
-## Security Fixes
-
-### Docker Image Security
-
-- **Alpine Package Upgrades** — Added `apk upgrade --no-cache` to builder stage to ensure latest security patches for base OS packages
-  - Fixes CVE-2026-22184 (zlib critical)
-  - Fixes CVE-2025-14524, CVE-2025-14819, CVE-2025-14017 (curl)
-
-### NPM Dependency Overrides
-
-- **Added `glob` override** — `^11.1.0` to fix CVE-2025-64756 (ReDoS vulnerability)
-
-### Build Fix
-
-- **Regenerated `package-lock.json`** — Fixed CI build failure caused by lock file desync with MCP SDK peer dependencies
-
----
-
-## Installation
-
-**npm:**
-
-```bash
-npm install -g memory-journal-mcp@3.1.1
-```
-
-**Docker:**
-
-```bash
-docker pull writenotenow/memory-journal-mcp:3.1.1
-```
-
----
-
-## Links
-
-- [Full Changelog](https://github.com/neverinfamous/memory-journal-mcp/wiki/CHANGELOG)
-- [v3.1.0 Release Notes](https://github.com/neverinfamous/memory-journal-mcp/releases/tag/v3.1.0)

package/releases/v3.1.2.md

@@ -1,40 +0,0 @@
-# v3.1.2 - CI/CD Pipeline Fix
-
-**Release Date:** January 11, 2026
-
-## Fixed
-
-### CI Build Pipeline
-
-- **Added `.npmrc` with `legacy-peer-deps=true`** — Resolves `npm ci` failures caused by optional peer dependency conflicts (vectra's zod@^3.23.8 vs our zod@^4.x)
-- **Root Cause**: The MCP SDK and vectra have differing zod peer dependencies, causing npm to fail strict peer dep resolution in CI
-- **Symptom**: `npm ci` error: `Missing: zod@3.25.76 from lock file`
-
-### Docker Workflow Gating
-
-- **Added `preflight-check` job to docker-publish.yml** — Tag pushes now run lint/typecheck/build before Docker deployment
-- **Root Cause**: Previous workflow condition `github.event_name == 'push'` bypassed lint-and-test on tag pushes
-- **Fix**: Tag deployments now require preflight checks to pass before building Docker images
-
----
-
-## Installation
-
-**npm:**
-
-```bash
-npm install -g memory-journal-mcp@3.1.2
-```
-
-**Docker:**
-
-```bash
-docker pull writenotenow/memory-journal-mcp:3.1.2
-```
-
----
-
-## Links
-
-- [Full Changelog](https://github.com/neverinfamous/memory-journal-mcp/wiki/CHANGELOG)
-- [v3.1.0 Release Notes](https://github.com/neverinfamous/memory-journal-mcp/releases/tag/v3.1.0)

package/releases/v3.1.3.md

@@ -1,64 +0,0 @@
-# v3.1.3 - Security Fixes for Docker Scout CVEs
-
-**Release Date:** January 11, 2026
-
-## Security Fixes
-
-### Docker Image CVE Remediation
-
-This release actively fixes several CVEs that Docker Scout flagged:
-
-#### npm Global Upgrade
-
-- **CVE-2025-64756** (glob, HIGH) — Fixed by upgrading npm globally in Docker build
-- **CVE-2025-64118** (tar, MEDIUM) — Fixed by upgrading npm globally in Docker build
-
-#### Alpine Edge Repository
-
-- **CVE-2025-14524** (curl, MEDIUM) — Fixed via Alpine edge: curl 8.18.0-r0
-- **CVE-2025-14819** (curl, MEDIUM) — Fixed via Alpine edge: curl 8.18.0-r0
-- **CVE-2025-14017** (curl, N/A) — Fixed via Alpine edge: curl 8.18.0-r0
-
-#### protobufjs CLI Cleanup
-
-- **CVE-2025-54798** (tmp, LOW) — Fixed by removing bundled protobufjs/cli deps and applying npm overrides
-- **CVE-2025-5889** (brace-expansion, LOW) — Fixed by removing bundled protobufjs/cli deps and applying npm overrides
-
-### Remaining Allowlisted CVEs (No Upstream Fix)
-
-These CVEs have **no fix available** from upstream:
-
-- **CVE-2026-22184** (zlib, CRITICAL) — Alpine has not released a fix version
-- **CVE-2019-10790** (taffydb, HIGH) — Package is 6+ years unmaintained/abandoned
-
----
-
-## Dockerfile Changes
-
-- Added `npm install -g npm@latest` to upgrade bundled npm
-- Added Alpine edge repository for curl security patches
-- Added protobufjs cli cleanup to force npm overrides
-- Copying `.npmrc` into build for consistent dependency resolution
-
----
-
-## Installation
-
-**npm:**
-
-```bash
-npm install -g memory-journal-mcp@3.1.3
-```
-
-**Docker:**
-
-```bash
-docker pull writenotenow/memory-journal-mcp:3.1.3
-```
-
----
-
-## Links
-
-- [Full Changelog](https://github.com/neverinfamous/memory-journal-mcp/wiki/CHANGELOG)
-- [v3.1.0 Release Notes](https://github.com/neverinfamous/memory-journal-mcp/releases/tag/v3.1.0)

package/releases/v3.1.4.md

@@ -1,32 +0,0 @@
-# v3.1.4 - npm Global Upgrade in Production Stage
-
-**Release Date:** January 11, 2026
-
-## Fixed
-
-### Docker Scout CVE-2025-64756 and CVE-2025-64118
-
-The v3.1.3 release added `npm install -g npm@latest` to the **builder stage** only, but the production stage uses a fresh `node:24-alpine` base image with its own bundled npm.
-
-**Fix:** Added `npm install -g npm@latest` to the **production stage** as well.
-
-This ensures the final Docker image has the latest npm with fixed versions of:
-
-- **glob** (fixes CVE-2025-64756, HIGH)
-- **tar** (fixes CVE-2025-64118, MEDIUM)
-
----
-
-## Installation
-
-**npm:**
-
-```bash
-npm install -g memory-journal-mcp@3.1.4
-```
-
-**Docker:**
-
-```bash
-docker pull writenotenow/memory-journal-mcp:3.1.4
-```

package/releases/v3.1.5.md

@@ -1,44 +0,0 @@
-# v3.1.5 - Remove protobufjs CLI to Eliminate taffydb CVE
-
-**Release Date:** January 11, 2026
-
-## Security Fixes
-
-### protobufjs CLI Removal
-
-The `protobufjs` package (transitive dependency via `@xenova/transformers → onnxruntime-web → onnx-proto`) includes a `/cli/` folder for `.proto` file compilation. This CLI folder contains unmaintained dependencies with known CVEs.
-
-**Since the CLI is not used at runtime**, we now remove it entirely from the Docker image:
-
-```dockerfile
-RUN rm -rf node_modules/protobufjs/cli
-```
-
-**CVEs Eliminated:**
-
-- **CVE-2019-10790** (taffydb, HIGH) — 6+ year old unmaintained package
-- **CVE-2025-54798** (tmp, LOW) — Symlink vulnerability
-- **CVE-2025-5889** (brace-expansion, LOW) — ReDoS vulnerability
-
-### Remaining Allowlisted CVEs (No Upstream Fix)
-
-These CVEs still have **no fix available** from Alpine:
-
-- **CVE-2026-22184** (zlib, CRITICAL) — Alpine hasn't packaged zlib 1.3.1.3 yet
-- **CVE-2025-60876** (busybox, MEDIUM) — Patch submitted to busybox but not released
-
----
-
-## Installation
-
-**npm:**
-
-```bash
-npm install -g memory-journal-mcp@3.1.5
-```
-
-**Docker:**
-
-```bash
-docker pull writenotenow/memory-journal-mcp:3.1.5
-```

package/releases/v4.0.0.md

@@ -1,71 +0,0 @@
-# v4.0.0 - GitHub Issue Lifecycle & MCP 2025-11-25 Compliance
-
-**Release Date:** January 16, 2026
-
-## Highlights
-
-This major release introduces **GitHub Issue Lifecycle Management** with automatic journal linking, full **MCP 2025-11-25 compliance** with structured output validation, and **Dynamic Context Management** enhancements. It also updates the minimum Node.js requirement to 24+.
-
-## Breaking Changes
-
-- **Node.js 24+ Required** — `engines.node` updated from ≥18.0.0 to ≥24.0.0
-- **Structured Output** — 5 tools now return `structuredContent` alongside text `content`. Clients that don't understand `structuredContent` will fall back to the text representation.
-
-## New Features
-
-### GitHub Issue Lifecycle Tools (+2 tools: 29→31)
-
-- **`create_github_issue_with_entry`** — Creates GitHub issue AND linked journal entry in one operation
-  - New `initial_status` parameter to set Kanban column (e.g., "Backlog", "Ready")
-  - Accepts `project_number` to auto-add issue to GitHub Project v2
-- **`close_github_issue_with_entry`** — Closes issue AND creates resolution entry with significance
-
-### New Resources (+2: 16→18)
-
-- **`memory://briefing`** (enhanced) — Now includes `userMessage` for agents to relay to users, template resource discovery, and client compatibility notes
-- **`memory://instructions`** (new) — Universal access to server behavioral guidance with tiered levels (`?level=essential|standard|full`)
-
-### New Prompt (+1: 14→15)
-
-- **`confirm-briefing`** — Session context acknowledgment for users to understand what context the agent received
-
-### MCP 2025-11-25 Compliance
-
-- **`outputSchema`** — 5 tools with structured output validation: `get_recent_entries`, `search_entries`, `search_by_date_range`, `get_entry_by_id`, `get_statistics`
-- **`lastModified` Annotations** — Dynamic resources now include ISO 8601 timestamps
-- **structuredContent + Text Fallback** — Tools return both structured JSON and formatted text for client compatibility
-
-## Bug Fixes
-
-- **Semantic Search Timing** — Fixed race condition where search returned 0 results immediately after rebuild
-- **Auto-Indexing** — New and updated entries are now immediately available for semantic search
-- **CI Status Discrepancy** — Resources now use latest _completed_ run for status determination
-- **GitHub Actions Resource** — `memory://actions/recent` now fetches live workflow runs from GitHub API
-- **Search Filter Accuracy** — Fixed `search_entries` ignoring filters when `query` is empty
-- **Vector Index Stats** — Fixed `memory://health` reporting 0 indexed entries after rebuild
-- **Trivy Security Scan** — Fixed workflow that hadn't run since September 2025
-- **Docker Latest Tag** — Fixed `latest` tag not being applied on `workflow_run` triggered builds
-
-## Documentation
-
-- Added hybrid workflow documentation explaining MCP + gh CLI approach for GitHub management
-- Enhanced wiki pages with Dynamic Context Management patterns
-- Documented AntiGravity IDE workarounds for clients that don't auto-inject ServerInstructions
-
----
-
-## Installation
-
-**npm:**
-
-```bash
-npm install -g memory-journal-mcp@4.0.0
-```
-
-**Docker:**
-
-```bash
-docker pull writenotenow/memory-journal-mcp:4.0.0
-```
-
-**Full Changelog:** [v3.1.5...v4.0.0](https://github.com/neverinfamous/memory-journal-mcp/compare/v3.1.5...v4.0.0)

package/releases/v4.1.0.md

@@ -1,88 +0,0 @@
-# Memory Journal MCP Server v4.1.0
-
-**Release Date:** January 17, 2026
-
-## Highlights
-
-- **Auto-rebuild Vector Index** — New `--auto-rebuild-index` CLI flag and `AUTO_REBUILD_INDEX` env var to synchronize vector index on server startup
-- **MCP Progress Notifications** — Long-running operations emit `notifications/progress` for improved UX
-- **MCP Icons Array Support** — 31 tools, 15 resources, and 15 prompts now include visual icons
-- **Expanded Structured Output** — Output schemas extended from 5 to 24 tools for programmatic consumption
-- **Kanban Automation** — `close_github_issue_with_entry` gains `move_to_done` parameter
-
----
-
-## Added
-
-### Auto-rebuild Vector Index on Startup
-
-- New `--auto-rebuild-index` CLI flag and `AUTO_REBUILD_INDEX` env var
-- Rebuilds vector index from all database entries during startup
-- Ensures `memory://health` reports accurate `itemCount` matching `entryCount`
-
-### `move_to_done` for `close_github_issue_with_entry`
-
-- New `move_to_done` boolean parameter (default: `false`)
-- Automatically moves Kanban item to "Done" column when closing an issue
-- New `project_number` parameter (uses `DEFAULT_PROJECT_NUMBER` if not specified)
-
-### MCP Progress Notifications
-
-- `rebuild_vector_index`: Reports progress every 10 entries
-- `restore_backup`: Reports 3-phase progress (backup → restore → verify)
-- `export_entries`: Reports 2-phase progress (fetch → process)
-- New utility module: `src/utils/progress-utils.ts`
-
-### MCP Icons Array Support
-
-- Tools, resources, and prompts include optional `icons` array
-- Follows MCP 2025-11-25 specification
-- Uses SVG data URIs for self-contained distribution
-
-### Expanded StructuredContent Coverage
-
-- 17 new output schemas (5 → 24 tools total)
-- Core Read, Mutation, GitHub, and Backup tool schemas
-- Clients supporting `structuredContent` receive validated JSON
-
-### `semantic_search` Hint Control
-
-- New `hint_on_empty` parameter (default: `true`)
-- Suppresses hints when `false` for programmatic consumers
-
-### PR Resource Empty Hints
-
-- `memory://prs/{pr_number}/entries` and `memory://prs/{pr_number}/timeline` include hints when no entries linked
-
----
-
-## Fixed
-
-- **`list_tags` Output Schema** — Fixed `usageCount` → `count` mapping
-- **`semantic_search` Hints** — Fixed always showing "No entries in vector index"
-- **`getRecentEntries` Ordering** — Added secondary sort by ID for deterministic results
-- **GHSA-73rr-hh4g-fpgx** — Patched npm's bundled `diff@8.0.2` → `8.0.3`
-- **CVE-2026-23745** — Patched npm's bundled `tar@7.5.2` → `7.5.3`
-- **`memory://health` Field Name** — Aligned `indexedEntries` → `itemCount`
-- **`memory://tags` Field Naming** — Mapped `usageCount` → `count`
-- **`create_github_issue_with_entry`** — Default status now "Backlog"
-- **`delete_entry` Vector Cleanup** — Removes entries from vector index
-- **Docker Security Gate** — Scan before push, `--only-fixed` for fixable CVEs
-- **Docker Build** — Reduced context by ~200MB with `.dockerignore` rewrite
-
----
-
-## Documentation
-
-- **GitHub Fallback Behavior** — Documented `requiresUserInput: true` response pattern
-- **`autoContext` Field** — Added "Field Notes" section explaining reserved field
-
----
-
-## Known Limitations
-
-- **Icons not visible in protocol output** — MCP SDK v1.25.2 doesn't pass icons through to responses. Server implementation is correct and future-ready.
-
----
-
-**Full Changelog:** https://github.com/neverinfamous/memory-journal-mcp/compare/v4.0.0...v4.1.0

package/releases/v4.2.0.md

@@ -1,90 +0,0 @@
-# Memory Journal MCP Server v4.2.0
-
-**Release Date:** January 17, 2026
-
-## Highlights
-
-- **HTTP/SSE Transport** — Run the server in HTTP mode for remote access and web-based clients
-- **New Tool: `cleanup_backups`** — Automatic backup rotation to prune old backups
-- **New Tool: `merge_tags`** — Tag normalization for consolidating similar tags
-- **100% StructuredContent Coverage** — All 33 tools now have formal output schemas
-- **Enhanced Feedback** — Improved hints for semantic_search, restore_backup, and PR timeline
-
----
-
-## Added
-
-### HTTP/SSE Transport
-
-- New `--transport http --port 3000` CLI options
-- `POST /mcp` — JSON-RPC requests (initialize, tools/call, resources/read, etc.)
-- `GET /mcp` — SSE stream for server-to-client notifications (supports resumability via `Last-Event-ID`)
-- `DELETE /mcp` — Session termination
-- **Stateful mode** (default): Session management via `mcp-session-id` header
-- **Stateless mode** (`--stateless`): No session management, ideal for serverless deployments
-- New dependencies: `express@^5.1.0`, `@types/express` (devDependency)
-
-### `cleanup_backups` Tool
-
-- `keep_count` parameter specifies how many recent backups to retain (default: 5)
-- Returns list of deleted filenames and count of kept backups
-- Added to `backup` tool group in ToolFilter
-
-### `merge_tags` Tool
-
-- Merge duplicate/similar tags (e.g., `phase-2` → `phase2`)
-- Source tag is deleted after merge; target tag created if not exists
-- Updates all entry-tag links and usage counts
-- Added to `admin` tool group in ToolFilter
-
-### Tool Count
-
-- **31 → 33 tools** (backup: 3 → 4, admin: 4 → 5)
-
----
-
-## Improved
-
-### `semantic_search` Hint Enhancement
-
-- Hint now includes the current `similarity_threshold` value (e.g., "0.3")
-- Suggests lowering threshold (e.g., "Try 0.2 for broader matches.")
-
-### `restore_backup` Enhanced Warning
-
-- Warning message now explicitly mentions tag merges, new entries, and relationships are reverted
-- New `revertedChanges` field in output with specific details
-- Added Field Note in `memory://instructions` documenting restore behavior
-
-### `memory://prs/{pr_number}/timeline` Enhancement
-
-- New `prMetadata` field with title, state, draft, mergedAt, closedAt, author, headBranch, baseBranch
-- New `timelineNote` field with human-readable PR status
-
----
-
-## Changed
-
-- **`memory://instructions` Default Level** — Changed from `standard` to `full` (~600 tokens)
-- **Briefing `clientNote`** — Simplified to "For complete tool reference and field notes, read memory://instructions."
-- **Expanded StructuredContent Coverage** — 7 additional tools now return `structuredContent` with Zod validation
-  - All 33 tools with response data now have formal output schemas
-
----
-
-## Fixed
-
-- **CI Status "unknown" for Cancelled Workflows** — Fixed `memory://briefing` and `memory://github/status` reporting "unknown" when latest workflow was cancelled
-  - CI status type now includes `passing | failing | pending | cancelled | unknown`
-
----
-
-## Documentation
-
-- **`memory://tags` vs `list_tags` Schema** — Documented intentional difference between resource and tool output
-- **Tag Naming Conventions** — Added guidance for consistent tag naming patterns
-- **`semantic_search` Threshold Guidance** — New Field Note documenting threshold recommendations
-
----
-
-**Full Changelog:** https://github.com/neverinfamous/memory-journal-mcp/compare/v4.1.0...v4.2.0

package/releases/v4.3.0.md

@@ -1,92 +0,0 @@
-# v4.3.0 - Causal Knowledge Graphs & Analytics
-
-Released: January 18, 2026
-
-## Highlights
-
-- **Causal Relationship Types** — 3 new relationship types for decision tracing and failure analysis
-- **Enhanced Analytics** — 4 additional metrics in `get_statistics` for deeper insights
-- **Significance Gradients** — Computed `importance` scores (0.0-1.0) for entries
-
----
-
-## Added
-
-### Causal Relationship Types
-
-Three new relationship types for building causal knowledge graphs:
-
-| Type         | Description                                               | Mermaid Arrow |
-| ------------ | --------------------------------------------------------- | ------------- |
-| `blocked_by` | Entry was blocked by another (e.g., blocker → resolution) | `--x`         |
-| `resolved`   | Entry resolved/fixed an issue from another                | `==>`         |
-| `caused`     | Entry caused or led to another outcome                    | `-.->`        |
-
-Updated Field Notes with guidance on when to use causal types.
-
-### Enhanced Analytics
-
-`get_statistics` now returns 4 additional metrics:
-
-- **`decisionDensity`**: Significant entries per period (entries with `significanceType`)
-- **`relationshipComplexity`**: Total relationships / total entries average
-- **`activityTrend`**: Period-over-period growth percentage
-- **`causalMetrics`**: Counts for `blocked_by`, `resolved`, `caused` relationships
-
-### Significance Gradients
-
-Computed `importance` scores (0.0-1.0) for entries based on:
-
-- Significance type (30%)
-- Relationship count (35%)
-- Causal relationships (20%)
-- Recency (15%)
-
-- `get_entry_by_id` now returns `importance` field
-- `memory://significant` resource sorts entries by importance (highest first)
-
----
-
-## Fixed
-
-### Docker Workflow Duplicate Builds
-
-Removed `push: tags: ['v*']` trigger that caused duplicate image sets when releasing versions.
-
-- Docker builds now only trigger via `workflow_run` after "Lint and Test" passes
-- Version tags still applied based on `package.json` version
-- Removed obsolete `preflight-check` job
-
----
-
-## Improved
-
-### `memory://significant` Secondary Sort
-
-Entries with equal importance scores are now sorted by timestamp (newest first), ensuring consistent chronological ordering for ties.
-
-### `create_entry` Auto-populates `issueUrl`
-
-When creating an entry with `issue_number` but no `issueUrl`, the URL is now auto-constructed from cached repository info. Requires GitHub integration and prior `getRepoInfo()` call.
-
-### Harmonized Graph Arrow Styles
-
-`memory://graph/recent` now uses the same arrow mappings as `visualize_relationships` tool:
-
-- Added causal types: `blocked_by` (--x), `resolved` (==>), `caused` (-.->)
-- Added missing types: `clarifies` (-.->) and `response_to` (<-->)
-- Standardized `implements` to use `==>` for consistency
-
----
-
-## Upgrade
-
-```bash
-# npm
-npm update -g memory-journal-mcp
-
-# Docker
-docker pull writenotenow/memory-journal-mcp:v4.3.0
-```
-
-**Full Changelog**: https://github.com/neverinfamous/memory-journal-mcp/wiki/CHANGELOG