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

Aberta
#2,316 0 comentários 14 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
1/5
Tempo estimado
Menos de uma hora
Facilidade para iniciantes
10/100
Tipo de issue
Documentação
Clareza
Precisa de esclarecimento
Status de atividade
Ativa
Stack de tecnologia
csharp
Domínio
release

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
C#
Estrelas
6.8k
Forks
778
Merge médio
22h 8min
PRs com merge (30d)
2

Preparar o ambiente

Abrir no Codespaces

Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de MessagePack-CSharp/MessagePack-CSharp

Todas as issues de MessagePack-CSharp/MessagePack-CSharp

Issues semelhantes

Mais issues de C#

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.