Whenever the dev
branch is updated (after merging a pull request), the Release
action is triggered. This action builds a nuget package with a prerelease identifier of the format -dev-nnnnn
appended to the version number. This package is automatically published on nuget.org.
-
On the
dev
branch, update CHANGES.md andVersionPrefix
in Serilog.Sinks.MSSqlServer.csproj. -
Create a PR to merge the
dev
branch intomain
. TheRelease
action will be triggered. This action builds a nuget package and publishes it on nuget.org. Additionally a release is created in the GitHub repo. The release summary will be taken from the description of the PR, so best thing is to put something similar to the version summary in CHANGES.md in there. -
After the release is done, increase the patch version number in
VersionPrefix
in Serilog.Sinks.MSSqlServer.csproj on thedev
branch. This ensures that the next dev release will have a higher version number than the latest release.
-
On the
dev
branch, update CHANGES.md and increase the major version inVersionPrefix
in Serilog.Sinks.MSSqlServer.csproj. Also setEnablePackageValidation
to false because on an intial release of a new major version you don't have a baseline version yet on nuget.org to compare with. -
Create a PR to merge the
dev
branch intomain
. TheRelease
action will be triggered. This works the same as described above under Normal Update. -
After the release is done make some changes in Serilog.Sinks.MSSqlServer.csproj on the
dev
branch. SetEnablePackageValidation
back to true andPackageValidationBaselineVersion
to the version of the new major release you just created (e.g. 7.0.0). Then also increase the patch version number inVersionPrefix
(e.g. 7.0.1).