Skip to content

Latest commit

 

History

History
27 lines (15 loc) · 1.64 KB

MAINTENANCE.md

File metadata and controls

27 lines (15 loc) · 1.64 KB
Raw

Creating a release

Serilog.Formatting.Log4Net uses MinVer for its versioning, so a tag must exist with the chosen semantic version number in order to create an official release.

  1. Update the CHANGELOG Unreleased section to the chosen version and copy the release notes for step #2.
  • Add the release date
  • Update the link from HEAD to the chosen version
  1. Create an annotated tag, the (multi-line) message of the annotated tag will be the content of the GitHub release. Markdown (copied from step #1) should be used.

git tag --annotate 1.0.0-rc.1

  1. Push the main branch and ensure that the build is successful.

git push

  1. Push the tag

    git push --follow-tags

Once pushed, the GitHub Continuous Integration workflow takes care of building, running the tests, creating the NuGet package, creating the GitHub release and finally publishing the produced NuGet package.

After the NuGet package is successfully published:

  1. Update the PackageValidationBaselineVersion element in the Serilog.Formatting.Log4Net.csproj file to the newly released version.
  2. Delete the CompatibilitySuppressions.xml file if there's one.