Skip to content

Latest commit

 

History

History
36 lines (25 loc) · 1.81 KB

BUILD.md

File metadata and controls

36 lines (25 loc) · 1.81 KB

How to build and publish TypeRefHasher

Most of the work is done by the Azure Pipeline, except for the publish to winget.

Release a new version to GitHub

To release a new version to Github, you need to push a tagged commit. Replace the version with the one you want to release. The Azure Pipeline does the rest.

git tag -a v1.0.0 -m "Release version 1.0.0"
git push origin v1.0.0

Release to winget

To release to winget-pkgs you need to release to Github first. If you have already done that and a new trh.msi is available on the Github Release page, you need to create a PR to winget.

  1. Clone the G DATA fork of the winget repo.
  2. Add a new manifests\g\GDATA\TypeRefHasher\VERSION\GDATA.TypeRefHasher.yaml file for the new version you want to release. Just copy an older version for that. You can find an example here.
    1. Update the PackageVersion tag to the new version.
    2. Update the InstallerUrl tag to point to the new trh.msi on Github Release.
    3. Update the InstallerSha256 of the trh.msi.
      1. Bash: curl -O -L https://github.com/GDATASoftwareAG/TypeRefHasher/releases/download/VERSION/trh.msi
      2. Bash: sha256sum trh.msi | tr '[:lower:]' '[:upper:]'

If you want to verify your changes you can test the manifest with the following commands:

# Check the schema of the manifest
winget validate <manifest>

# Install the package locally.
winget install -m <manifest>

If you are sure that your manifest works, create a PR to the official winget-pkgs repository.