[BUG] Use clearer unique git tag info for MSIX Core preview releases

Project
MSIX SDK

Describe the bug
I receive email notifications for MSIX Core preview releases with differing changelog information, yet all release notices refer to identical git tag info: microsoft/msix-packaging - Tag: MSIX-Core-preview - Commit: 16737c0 , and a non-incrementing artifact number msixmgrSetup-1.1.56.0-x64.msi. It would help users and packagers if a unique git commit id and incrementing version number accompanied each release notification or instructions were provided on how to find that information in git history and tags.

To Reproduce
Subscribe to github notifications for releases and receive emails.

Expected behavior
Emails announcing new releases should include a unique git commit id identifying that particular release. For users or packagers tracking the preview releases, including a unique git content hash and/or tag identifier is essential for packaging automation tools to work.

Screenshots
Emails containing microsoft/msix-packaging - Tag: MSIX-Core-preview - Commit: 16737c0 , and non-incrementing artifact number msixmgrSetup-1.1.56.0-x64.msi.

Platform

Additional context
I would like to make RPM packaging for msix-packaging. Even in the prerelease phase, using incrementing version numbers or at a minimum unique git content identifier for all releases would be very helpful for this purpose. I would also like to know the "base version" that this prerelease is expected to use when it reaches general release. Is it 1.1.56.0?

Start by reviewing the MSIX Core preview release notifications, the MSIX-Core-preview tag, commit 16737c0, and the msixmgrSetup-1.1.56.0-x64.msi artifact version. Determine how preview tags and artifact versions are produced, then make each release identifiable by a unique commit or tag and an incrementing version, while documenting the expected base version for general release.