-
-
Notifications
You must be signed in to change notification settings - Fork 11
How to: Prepare a release
Martin Steinisch edited this page Nov 16, 2019
·
2 revisions
- Create a milestone with the full version number
MAJOR.MINOR.PATCH(-SUFFIX)
in the official repo: - Create a branch
release/MAJOR.MINOR
in the official repo:- Merge the previous release branch into current release branch (it contains differences in
appveyor.yml
). - Merge master branch into current release branch.
- Bump
version
andversion_suffix
inappveyor.yml
in current release branch. - Verify that everything builds correctly.
- Merge the previous release branch into current release branch (it contains differences in
- Create the final build artifacts:
- Set the environment variable
ARTIFACT_SIGNING_ENABLED
on https://ci.appveyor.com totrue
. - Trigger a re-build on appveyor.com. The artifacts are automatically uploaded to https://signpath.io.
- Set the environment variable
ARTIFACT_SIGNING_ENABLED
on https://ci.appveyor.com back tofalse
. - Log in to https://signpath.io, verify and approve the signing request.
- Download the signed artifacts.
- Set the environment variable
- Create a release
Version MAJOR.MINOR.PATCH(-SUFFIX)
in the official repo:- Tag the version with
vMAJOR.MINOR.PATCH(-SUFFIX)
on current release branch. - Attach the signed artifacts.
- Tag the version with
- Upload the signed NuGet package to https://www.nuget.org.