Announcement: v4 preview.2, and the repository moving to Cysharp at v4 release

Open
#2,316 0 comments 14 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
10/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Active
Tech stack
csharp
Domain
release

Research direction

This issue is an announcement and does not identify a code change, file, or test to work on. Read the linked v4 README and migration guide for context; there is no completion criterion or contribution task specified here.

Written by the indexing model from the issue text.

Description

MessagePack for C# v4 preview.2 is now available on NuGet.

v4 is a complete redesign of MessagePack for C#: more than twice the performance, stronger safety defaults, full Native AOT support and many new features, including support for C# 15 union types, while staying wire-compatible with v3. The basic API shape is the same, but there are breaking changes. See the v4 README for an overview, and the migration guide for moving from v3.

Please give it a try, and let us know how it goes: bug reports and feedback in the issues are very welcome.

If nothing major comes up, we plan to ship v4.0.0 in mid-to-late November, after .NET 11 is released.

The repository is moving to Cysharp

With the v4 release, this repository will move to the Cysharp organization, the company I work for. This has been agreed among the maintainers, and v4 will be maintained by me and Cysharp.

What stays the same:

  • MessagePack for C# remains open source under the MIT license.
  • It remains a .NET Foundation project.
  • v3 keeps its current maintenance, and security fixes will continue.
  • The NuGet package IDs and the MessagePack namespace do not change.
  • GitHub redirects the current repository URL, so existing links, clones and forks keep working.

Why

A serializer that so many applications depend on needs steady, long-term development, and that takes dedicated funding and engineering time. Moving the project to Cysharp lets us commit both to it.

Thank you to everyone who has used MessagePack for C#, reported issues and contributed over the years. If you have questions or concerns about the move, please leave them in this issue.

Dominant language
C#
Stars
6.8k
Forks
778
Avg merge
22h 8m
Merged PRs (30d)
2

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MessagePack-CSharp/MessagePack-CSharp

All issues in MessagePack-CSharp/MessagePack-CSharp

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.