search

Xabaril / AspNetCore.Diagnostics.HealthChecks

Enterprise HealthChecks for ASP.NET Core Diagnostics Package
Apache License 2.0
3.98k stars 769 forks source link

Versioning #2006

Open sungam3r opened 10 months ago

sungam3r commented 10 months ago

Now all versions are written into build/version.props file. When making changes in some project you have to remember to bump corresponding version in that file. It's not convinient. Moreover, it's more unconvinient for PRs from dependabot like this one https://github.com/Xabaril/AspNetCore.Diagnostics.HealthChecks/pull/2001. At the end when preparing for release maintainer needs to manually check all versions. This process shoul be simplified in some way.

michaelmairegger commented 4 months ago

We should move to centrac package management. Then we can manage all the versions in one file. I can provide a PR if desired

luizbon commented 1 month ago

I see two mixed pieces of information here in this issue. One is as a maintainer controlling the package versions and how this can be simplified. Another one is the project dependencies and using bots to keep them updated.

A SemVer approach could help with the first one. Maybe introducing MinVer, which controls versions based on Git Tags (closely related to GitHub releases), helps.

For the second one, the logical approach is introducing CPM (Central Package Management), native to NuGet.

Does that sound right, @sungam3r?