Skip to content

chore: merge upstream thedotmack/claude-mem v12.3.9#16

Merged
Dee-0503 merged 1 commit into
mainfrom
upstream-merge-v12.3.9
Apr 24, 2026
Merged

chore: merge upstream thedotmack/claude-mem v12.3.9#16
Dee-0503 merged 1 commit into
mainfrom
upstream-merge-v12.3.9

Conversation

@Dee-0503
Copy link
Copy Markdown
Owner

Summary

  • Sync 30 commits from upstream thedotmack/claude-mem (v12.3.2 → v12.3.9)
  • Resolves the Ceemac Upstream Sync CI failure that has been failing for 7 consecutive runs due to merge conflicts

Key upstream changes included

Conflict resolution (25 files)

  • 8 version/config: took upstream versions, preserved our ci:non-green-email script
  • 4 build artifacts: took upstream (will be rebuilt on next npm run build)
  • 13 source files: took upstream since our fork's unique additions (maintenance, CI email) are in separate non-conflicting files

Test plan

  • bun test tests/maintenance/ — 12 pass, 0 fail (our additions preserved)
  • bun test tests/worker/agents/response-processor.test.ts — 26 pass, 1 pre-existing upstream failure
  • Manual: verify npx claude-mem maintenance status still works after merge
  • Verify Ceemac Upstream Sync workflow succeeds on next scheduled run

Sync 30 commits from upstream (v12.3.2 → v12.3.9):
- Issue Blowout 2026: 25 bug fixes (thedotmack#2083)
- PID reuse detection for container restarts (thedotmack#2082)
- Remove bearer auth and platform_source filter (thedotmack#2081)
- Security observation types + Telegram notifier (thedotmack#2084)
- Per-user port derivation, FTS5 query escaping, RestartGuard

All 25 merge conflicts resolved:
- 8 version/config files: took upstream versions
- 4 build artifacts: took upstream versions
- 13 source files: took upstream (our fork changes in separate files)

Maintenance tests: 12 pass / 0 fail
@Dee-0503 Dee-0503 enabled auto-merge April 24, 2026 14:11
@Dee-0503 Dee-0503 merged commit 1ca76f2 into main Apr 24, 2026
4 checks passed
Dee-0503 added a commit that referenced this pull request Apr 25, 2026
The upstream merge (PR #16) incorrectly resolved hooks.json conflicts
by keeping the fork's old version without per-user port logic. This
caused startup hook failures when the worker port derived by
hooks.json (37700 + uid%100) didn't match the hardcoded 37777.

Take upstream's hooks.json which reads CLAUDE_MEM_WORKER_PORT from
settings.json first, then falls back to per-user derivation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant