NuGet packages versioning scheme

[andrerav]

Currently the NuGet packages published have the following versions:

Package	Version
Mapster	7.4.2-pre02
Mapster.Async	2.0.3-pre02
Mapster.Core	1.2.3-pre02
Mapster.DependencyInjection	1.0.3-pre02
Mapster.EF6	2.0.3-pre02
Mapster.EFCore	5.1.3-pre02
Mapster.Immutable	1.0.3-pre02
Mapster.JsonNet	1.1.3-pre02
Mapster.Tool	8.4.2-pre02

Keeping all these version numbers up to date is a bit of a hassle when doing a release. It also feels unecessary since we usually release all these packages at the same time anyway.

Proposal: Should we simply align all the packages with the .NET version cycle and append a build number at the end?

Package	Version
Mapster	9.0.0.xyz
Mapster.Async	9.0.0.xyz
Mapster.Core	9.0.0.xyz
Mapster.DependencyInjection	9.0.0.xyz
Mapster.EF6	9.0.0.xyz
Mapster.EFCore	9.0.0.xyz
Mapster.Immutable	9.0.0.xyz
Mapster.JsonNet	9.0.0.xyz
Mapster.Tool	9.0.0.xyz

This would be a step towards automating versioning and package releases using workflows (i.e automatically create version tags + create release + push NuGet packages).

@stagep @DocSvartz Let me know what you think.

[DocSvartz]

@andrerav Looks good.
But when analyzing the issue, will have to constantly check the list of releases.
.xyz - This part, as far as I understand, will be random?

[andrerav]

We can configure this however we like. There are a few different options:

1. 9.0.0.xyz: Here, xyz would be a build number
2. 9.0.X: In this case, X is just an auto-incrementing number starting at 0
3. 9.0.X.xyz - A combination of 1 and 2.

There are other alternatives as well.

In any case, we should keep adding -pre01, -pre02 when releasing from the development branch.

The .NET runtime versioning scheme is a good example to follow: https://versionsof.net/core/8.0/

[DocSvartz]

@andrerav I think dont understood correctly what a build number :)
if https://www.nuget.org/packages/Microsoft.Extensions.Diagnostics.HealthChecks

9.0.0-preview.7.24406.2
{24406.2} is build number
I think it's appropriate to use it in pre-release versions.

And for releases use this approach

9.0.X: In this case, X is just an auto-incrementing number starting at 0

But it will probably be even more difficult than now

[andrerav]

I think it should be doable. Or at least something very similar. The goal is to automate this completely using github workflows.

[alxNoComment]

its cool
waiting release!

[andrerav]

Hi @alxNoComment There are prerelease packages available on NuGet if you want to try out the latest changes and fixes :)