Releasing

1. First, make sure your local repo is fully up-to-date.

git checkout main
git pull

2. Run gitversion to get the version tag from the "InformationalVersion" property. Example: 0.1.0-ci.102+Branch.main.Sha.f32c6464d690df26e059321c9168f09d12b99e99.

gitversion

3. Create a tag with the version number and push it.

git tag -a <version> -m "<version>" 
git push origin <version> 

4. The CD workflow will pick up the release, build and upload the MSIs to the Assets of the Release.

5. Go to the Releases edit the draft release.

• Add release notes using the "Auto-generate release notes".
• Remove all entries that are bugs within the release itself (ones that were never public).
• Uncheck "This is a pre-release".
• Check "This is the latest release".
• Publish the release.
• Copy the link to Microsoft.Tools.Teammate.msi to your notes (e.g. https://github.com/microsoft/TeamMate/releases/download/0.1.1-ci.111%2BBranch.main.Sha.610914adb6897c1dea5ecd33af94e71c29b39a33/Microsoft.Tools.TeamMate.Production.msi). Will be needed below.

6. If you have not installed wingetcreate, do so now:

winget install wingetcreate

7. Create the new manifest using wingetcreate. Note that by passing "-i", you will be prompted interactively to enter the installer URI (from above), etc./

wingetcreate.exe update -i -v <new version, e.g.: 0.1.3> -s Microsoft.TeamMate

8. If for some reason the manifest is created but not submitted, submit the new manifest as a PR to microsoft/winget-pkgs:

wingetcreate.exe submit <path to manifest, e.g.: c:\temp\manifests\m\Microsoft\TeamMate\0.1.3>

9. Go through the approval process with the PR. Be patient, their volume is large, and they are doing their best.

10. Update GitVersion.yml in TeamMate with the next version and send a PR.

11. Done.