Add back 'beta2' nuget moniker for official builds. #19546
Conversation
|
@tmeschter @jasonmalinowski @dotnet/roslyn-infrastructure @jasonmalinowski: I am assuming explicit ask mode approval is not required for this change since this is infrastructure - but let me know if that's not a valid assumption. |
|
This does impact shipping bits (we stamp this in binaries today) so we should go through ask mode process. |
|
Tagging @MattGertz for ask mode approval Customer scenario An earlier commit accidentally merged some code that caused the version moniker for all Roslyn nuget packages to change from 'beta2' to 'dev'. For example, the package versions went from 2.3.0-beta2-61715-06 to 2.3.0-dev-61715-06. This change fixes the moniker back to 'beta2'. Customers depend on the names of our nuget packages and shipping with opaque version moniker 'dev' would make it hard for users to figure out what release the package really maps to. Bugs this fixes: Workarounds, if any Risk Performance impact Is this a regression from a previous update? Root cause analysis: How was the bug found? |
|
@dotnet-bot test this please |
* Update `RoslynAssemblyVersionBase` from 2.3.0 to 2.6.0 * Update `RoslynFileVerionBase` from 2.3.0 to 2.6.0 * Reset `RoslynNuGetMoniker` to beta1 Also incorporate @shyamnamboodiripad's fix in dotnet#19546.
|
@dotnet-bot test windows_debug_vs-integration_prtest please |
Add back the 'beta2' nuget package moniker for official builds.
The moniker was accidentally removed in a2e2bf4 (PR #19469).