release: v0.1.26 — legacy .server.pid teardown hotfix#441
Merged
Conversation
Single-fix hotfix. Brings #439 (closes #437) to PyPI so 0.1.25 users hitting the "pre-0.1.25 install" phantom lock error get a clean upgrade path. Follow-up axis (live orphan holder + stderr UX + child lifecycle) tracked separately in #440; not bundled here to keep the release diff minimal. 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 legacy
.server.pidstale-file race landed in #439 (closes #437).Single fix — no new features, no API changes. 0.1.25 users hitting the "another memtomem-server holds a lock (likely a pre-0.1.25 install)" error intermittently on Claude Code
Reconnect/claude mcp listget a clean upgrade path.Changes in this release
bumped packages/memtomem/pyproject.toml: 0.1.25 → 0.1.26bumped uv.lock workspace entryCHANGELOG: [Unreleased] → [0.1.26] — 2026-04-24Feature commit (already on
main): #439 —fix(server): unlink legacy .server.pid on atexit and SIGTERM (closes #437).Out of scope (follow-up)
Release mechanics
git tag test-v0.1.26a1 <merge-sha> && git push origin test-v0.1.26a1, approvepypienvironment, confirm on test.pypi.org.git tag v0.1.26 <merge-sha> && git push origin v0.1.26, approve, confirm on pypi.org.gh release create v0.1.26 --title "v0.1.26" --notes-file ....Per
project_release_workflow.md: behavior-change releases get a TestPyPI dry-run. This one touches process-teardown semantics on POSIX, covered by the existingtest_server_sigterm.pysuite plus a new legacy-unlink end-to-end case, all green on CI. Dry-run is still recommended to verify the wheel on a freshuv tool installbefore flipping PyPI.🤖 Generated with Claude Code