Skip to content

Bump version to 4.1.0 - #7

Open
zacala1 wants to merge 1 commit into
mainfrom
release/4.1.0
Open

zacala1 wants to merge 1 commit into
mainfrom
release/4.1.0

Conversation

@zacala1

@zacala1 zacala1 commented Oct 24, 2026 •

Copy link
Copy Markdown
Owner

Summary

main still says <Version>4.0.0</Version>, but it contains more than the 4.0.0 release (4aec041): the net10.0 build, Global\ / Local\ region names, same-thread two-instance detection and the Auto-layout fingerprint. A pack from main would produce a package named 4.0.0 that differs from the released one.

  • InterprocessMemory.csproj: <Version> 4.0.0 -> 4.1.0, and PackageReleaseNotes now describe 4.1.0 (they described version 4 before).
  • README.md: two statements that hold for every 4.x version say "4.x" instead of "4.0.0" (format version 3 is still written; 3.0.0 must not share a region with any 4.x version on Linux).

Left as they are on purpose:

  • The README and MIGRATION install lines stay at --version 4.0.0 until 4.1.0 is published.
  • The CHANGELOG section stays 4.1.0 (not released yet); it gets its date when the tag is created.

Verification

  • The csproj parses as XML; version and release notes read back as expected.
  • CI on 437d1ce is green on Linux and Windows. The Linux pack step created InterprocessMemory.4.1.0.nupkg and .snupkg (package artifact, 182,491 bytes, about twice the net8.0-only 4.0.0 package). Both frameworks ran the tests.
  • Not checked: the file list inside the nupkg (lib/net8.0 and lib/net10.0), because the artifact download host is blocked from the environment that prepared this PR. Check it before publishing: unzip -l InterprocessMemory.4.1.0.nupkg | grep lib/.

No code changes. Not tagged, not published.

main carries more than 4.0.0 (net10.0 build, Global\/Local\ region names,
same-thread two-instance detection, Auto-layout fingerprint), so packing it
under 4.0.0 would produce a package that differs from the 4.0.0 release at
4aec041. Release notes now describe 4.1.0. The README mentions 4.x instead of
4.0.0 where the statement holds for every 4.x version; the install line stays
at 4.0.0 until 4.1.0 is published. The CHANGELOG section keeps "not released
yet" and gets its date when the tag is created.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants