release: v0.1.27 — legacy flock LOCK_SH hotfix#446
Merged
Conversation
…xistence Single-fix hotfix. Brings #445 (closes #444) to PyPI so 0.1.26 users who hit "one Claude Code session blocks all others" get a clean upgrade path. Co-Authored-By: Claude <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Hotfix release for the multi-instance bug landed in #445 (closes #444).
Single fix, no new features. 0.1.26 users who tried to use
memtomemin more than one Claude Code session simultaneously (e.g. different projects) hit "Failed to connect" on every session after the first — because_try_hold_legacy_flocktookLOCK_EXandsys.exit(1)'d on contention. 0.1.27 swaps that forLOCK_SH: two 0.1.26+ servers coexist, pre-0.1.25 cross-version mutex is preserved.Changes
packages/memtomem/pyproject.toml:0.1.26 → 0.1.27uv.lockworkspace entryCHANGELOG: [Unreleased] → [0.1.27] — 2026-04-24Feature commit on
main: #445.Release mechanics
test-v0.1.27a1tag → approvepypienv → verify on test.pypi.org.v0.1.27tag → approve → verify on pypi.org.gh release create v0.1.27.Per
project_release_workflow.md, behavior-change releases get a dry-run. This one touches process-lifecycle semantics on POSIX, covered by thetest_server_sigterm.pysuite including a live two-subprocess coexistence test. Dry-run still recommended.🤖 Generated with Claude Code