Repository navigation
Release 4.0.0: date the changelog entry - #4
Merged
Merged
Conversation
Everything the entry lists is on main and passes CI on Linux and Windows (the pack step builds InterprocessMemory.4.0.0.nupkg and .snupkg). Tagging and publishing the package are separate steps.
This was referenced Oct 22, 2026
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Replaces "4.0.0 (not released yet)" in
CHANGELOG.mdwith the date, 2026-10-22. Nothing else changes: the version number,MIGRATION.md, the README and the package metadata already say 4.0.0 since #3.main(a2f3e16) passed CI on Linux and Windows, and the Linux job's pack step producedInterprocessMemory.4.0.0.nupkgand.snupkg.If the tag is created on a later day, change the date in this PR before merging.
After merging (not done by this PR)
Draft text for the GitHub release
InterprocessMemory 4.0.0
Fixes lock handling, torn reads, region creation races and several crash hazards found in three code reviews. The memory format is unchanged (format version 3).
Breaking:
StructuredMemory<T>.WriteLock/ReadLockareref structs: noawaitinside a lock scope (it is a compile error now). Recompile against 4.0.0.OrphanLockTimeoutdefaults to disabled; a lock whose owner process exited is still recovered.MemoryRegion.Remove).StructuredMemory<T>.OpenExistingchecks the schema version before the size;FilePathmode rejects a file of another size instead of growing it.Important fixes:
SharedArray<T>/StructuredMemory<T>values could be read torn by another process./dev/shmout of space (SIGBUS), PID namespaces of containers,Disposeracing waiting threads.New:
MemoryRegion.Remove,MemoryRegion.ForceResetLocks,MemoryRegion.DisposeGracePeriod,MemoryRegionOptions.UnixCreateMode,LockOwnerInfo.ReaderCount,SharedArray<T>lock guards.See
CHANGELOG.mdfor every change andMIGRATION.mdfor the upgrade notes.Generated by Claude Code