When we run the build on AppVeyor we also create the NuGet packages (artifacts) that we then manually deploy to NuGet. By manually I mean that we log into the AppVeyor web side and deploy from a given build.

There is also some manual work around creating the artifacts that should go on the GitHub release page.

My suggestion is that we try to automate most of this stuff so that we can release often and with basicaly no effort on our side.

What we did in LightInject for instance, is that we deploy on repo_tag meaning that if we push a new tag it triggers the deployment of the package to NuGet.

In our case here it would involve the following.

• Deploy NuGet packages
• Deploy Choco package
• Deploy to Github releases with a draft release possible drafted by something like github-changelog-generator that can be manually edited on Github

We can then publish the whole thing by simply doing

git tag 0.15.0
git push --tags

Publishing artifacts to GitHub Releases
https://www.appveyor.com/docs/deployment/github/