-
Notifications
You must be signed in to change notification settings - Fork 736
Use V3 for DncEng BAR publishing #3731
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Test promotion build -> https://dev.azure.com/devdiv/DevDiv/_build/results?buildId=4184770&view=results |
|
I'd run one more build to make sure that looks correct in the merged manifest, but LGTM otherwise. |
|
@zivkan is running an another build. I will post my result here after. |
|
|
||
| <PropertyGroup Condition=" '$(Version)' == '' "> | ||
| <Version>$(SemanticVersion)$(PreReleaseInformationVersion)</Version> | ||
| <Version Condition="'$(BUILD_SOURCEVERSION)' != '' AND '$(IsCommandLinePackage)' != 'true'">$(SemanticVersion)$(PreReleaseInformationVersion)+$(BUILD_SOURCEVERSION)</Version> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In case anyone in my team sees this and wonders why, there's no benefit to adding the commit hash to the end of the string. Looking at nuget.org, no other packages do this, including System.* packages from the dotnet team. Our nuspec still has the commit hash, to enable source link, so anyone who really wants the commit hash can still get it.


V3 onboarding
This PR uses maestro.task from general testing