chore(deps): bump mcp-mux/muxcore v0.19.0 → v0.19.7 (drop-in)#182
Conversation
Three mcp-mux releases landed since v0.19.3 (prior engram baseline was actually v0.19.0 per go.mod). Drop-in for engram — zero consumer code changes required. Engram uses the legacy Handler path (not SessionHandler) and does not host the mcp-mux daemon, so the two primary production bugs motivating the chain (keepalive spec violation + zombie-listener) are not directly triggerable. However the release contains one correctness fix that benefits engram even on the legacy path: - upstream.Process.ReadLine now normalises os.ErrClosed -> io.EOF. exec.Cmd.StdoutPipe closes the pipe after cmd.Wait returns, and Start runs Wait in a background goroutine concurrent with external ReadLine. Fast-exiting upstreams previously surfaced 'read |0: file already closed' which is semantically EOF. Engram subprocesses that exit quickly (tests, short health probes) now see the cleaner error path. Plus forward-compat value — once engram moves to the daemon/SessionHandler path per the 2026-04-12 architecture decision, fixes from v0.19.5/6/7 are already on board. Release notes: - https://github.com/thebtf/mcp-mux/releases/tag/muxcore/v0.19.5 - https://github.com/thebtf/mcp-mux/releases/tag/muxcore/v0.19.6 - https://github.com/thebtf/mcp-mux/releases/tag/muxcore/v0.19.7 Verified: - go build ./... — clean - go vet ./... — clean - go test -short -count=1 ./... — all unit tests pass (integration suites skip cleanly without DATABASE_DSN) Closes engram issue #87.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
ОбзорОбновлена версия зависимости Go-модуля Изменения
Возможно связанные PR
Предлагаемые метки
Оценка трудозатратности кода🎯 1 (Тривиально) | ⏱️ ~2 минуты Стихотворение
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 golangci-lint (2.11.4)Error: can't load config: unsupported version of the configuration: "" See https://golangci-lint.run/docs/product/migration-guide for migration instructions Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
1 participant
Closes engram issue #87.
Drop-in dependency bump — zero consumer code changes. See commit message for release-note details (3 releases chain: v0.19.5/6/7).
Verified
go build ./...— cleango vet ./...— cleango test -short -count=1 ./...— all unit tests green (integration tests skip without DATABASE_DSN)Why MEDIUM priority
Engram uses the legacy
Handlerpath, notSessionHandler. The two primary production bugs in the chain don't trigger here. BUT the v0.19.7 fix forupstream.Process.ReadLinenormalisingos.ErrClosed -> io.EOFdoes help — engram subprocesses that exit quickly get a cleaner error path. Plus forward-compat for the daemon/SessionHandler migration (2026-04-12 architecture decision).No impact on US3
This PR is off
mainand independent of PR #181 (US3 observations split). No scope overlap, no file conflicts.Summary by CodeRabbit