Rzls - CI - Release Tagging

[tris203]

When building rzls from source, there doesn't appear to be a way to connect the VS Code executable version to a specific commit. This makes it challenging to trace the origin of a particular release.

Would it be possible for the CI process to create a tag for each release, ensuring that it corresponds to a specific commit? Alternatively, could the section linked below be updated to include a step for tagging the commit when a version is "released" into VSCode-CSharp?

Reference: Inserting Razor Into VSCodeCSharp Documentation

[davidwengier]

Not withstanding the validity of the request, a couple of things that might help anyone interested in finding out in the meantime:

• The commit SHA will be in the properties of rzls.dll if you go digging in your hard drive:
  
• The change log in the C# extension repo should link to the PR that updates the Razor bits, which should link to the commit. eg Bump razor to 25052.3 vscode-csharp#7904 though granted this is manual and we might not be perfect at it every time :)