You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Calculate version number dynamically
- Support pushing prerelease versions on NuGet
- Reduce downstream maintenance efforts by fixing the version number to MAJOR.0.0.0
- Create GitHub releases for everything that's pushed to NuGet
This library uses [Nerdbank.GitVersioning](https://github.com/AArnott/Nerdbank.GitVersioning) for generating stable and reproducible version numbers.
6
+
7
+
The so-called base version is manually maintained in [the version config](version.json). Every build calculates its final version number based on the base version and the number of changes that occured since the last change to the version config.
8
+
9
+
The base version represents the _next_ version that we will released. During development it contains a prerelease suffix, like `-beta` which is appended to the generated NuGet packages.
10
+
11
+
Every successful commit on `master` deploys packages to `nuget.org` and a creates GitHub release. As long as we have the prelease suffix both will be marked as such.
12
+
13
+
### Release workflow
14
+
15
+
1. Remove prelease suffix from `version.json`.
16
+
1. Wait for the completion of the deployment.
17
+
1. Remove the prerelease flag from the newly created GitHub release.
18
+
1. Increment the version number in `version.json` and again add the prelease suffix (usually `beta` is fine).
0 commit comments