-
Notifications
You must be signed in to change notification settings - Fork 521
Creating and deploying a new version
Yaakov edited this page Feb 9, 2019
·
8 revisions
- Ensure all Samples run correctly
- Ensure all unit tests pass
- Ensure CI passes
- Update the version number in
AssemblyInfo.cs. - Update the release notes URL (
PackageReleaseNotes) in the csproj. - Add a section for the new version to the top of
changes.txt. - Commit and tag the release with
git tag. The tag should beX.Y.Z, i.e. the raw version number. For a prerelease, useX.Y.Z-suffix, e.g.2.0.0-beta.4. - Run
git pushto updateHEADon themasterbranch. - Run
git push --tagsto push the new commits and tag. If you want to push just your new tag, usegit push origin tag-name. - Add a changelog to the automatically-created GitHub Release. This should match
changes.txt. - Publish the GitHub Release.
- If any other SteamRE projects (e.g. DepotDownloader) require the newer version, update the NuGet dependency and make any other required code changes.