Summary
The latest published release on main is v0.5.2 (2026-06-08). Since then, #267 (KSM doctor check + memfd probe evidence) has landed on main, and other fixes may have queued behind it as well.
We pin the forkd version we ship against to the latest release tag rather than main. Right now that means we're effectively pinned to v0.5.2 even though #267 (and any follow-ups) are already merged. A v0.5.3 tag would let us pull the KSM doctor check + the "memfd MAP_SHARED is not the right path for #5" finding into our pinned build.
What's in v0.5.2 vs what's on main
Request
If the main branch is in a releasable state, would a maintainer be willing to cut a v0.5.3 tag? Happy to help draft release notes against git log v0.5.2..HEAD if useful.
No pressure on timing — whenever it's convenient to bundle it with the next planned release is fine.
Context
We're integrating forkd as the sandbox provider behind fabro PR #567 and currently pin to the latest release. The v0.5.3 tag is the smallest change that lets us absorb the post-v0.5.2 work without a main pin.
Summary
The latest published release on
mainis v0.5.2 (2026-06-08). Since then, #267 (KSM doctor check + memfd probe evidence) has landed onmain, and other fixes may have queued behind it as well.We pin the forkd version we ship against to the latest release tag rather than
main. Right now that means we're effectively pinned to v0.5.2 even though #267 (and any follow-ups) are already merged. A v0.5.3 tag would let us pull the KSM doctor check + the "memfdMAP_SHAREDis not the right path for #5" finding into our pinned build.What's in v0.5.2 vs what's on
mainmainsince:MAP_SHAREDapproach for KSM directed hints for fork families #5, narrows the next implementation attempt)Request
If the
mainbranch is in a releasable state, would a maintainer be willing to cut a v0.5.3 tag? Happy to help draft release notes againstgit log v0.5.2..HEADif useful.No pressure on timing — whenever it's convenient to bundle it with the next planned release is fine.
Context
We're integrating forkd as the sandbox provider behind fabro PR #567 and currently pin to the latest release. The v0.5.3 tag is the smallest change that lets us absorb the post-v0.5.2 work without a
mainpin.