{"push_id":1185565160,"size":1,"distinct_size":1,"ref":"refs/heads/fix-build-versioning","head":"3a45c4337bb6918cf4997c913c0c1f42d956d844","before":"0125b03c784e6d44058d5d314ce7092aff3361a5","commits":[{"sha":"3a45c4337bb6918cf4997c913c0c1f42d956d844","author":{"name":"Jason Malinowski","email":"b4c93731a220e4df123a6d97c0acb20c23a2c6cd@microsoft.com"},"message":"Tweak how we specify versions in VSL.Versions.targets\n\n- Introduce a new variable, RoslynFileVersionBase, which specifies the\n  file version base we will use. This controls the file version as\n  stamped in the PE, and also the version that's used for our NuGet\n  packages.\n- Rename RoslynSemanticVersion to RoslynAssemblyVersionBase so it's\n  more clear what that's used for.\n- Ensure that the PE file version header changes for each day, to give\n  some protection that build-to-build upgrade correctly works for\n  MSI-based installs, and also for sanity so you can have some hope\n  when looking at a binary on disk.","distinct":true,"url":"https://api.github.com/repos/jasonmalinowski/roslyn/commits/3a45c4337bb6918cf4997c913c0c1f42d956d844"}]}
{"actor":{"display_login":"jasonmalinowski"}}