From fef328a63a0800f266674f254500b512366b4dbe Mon Sep 17 00:00:00 2001
From: Tom Meschter <tom.meschter@microsoft.com>
Date: Mon, 15 May 2017 20:49:23 -0700
Subject: [PATCH] Update version numbers

* 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 #19546.
---
 build/Targets/Versions.props | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/build/Targets/Versions.props b/build/Targets/Versions.props
index 3287c9342ed..a6a0342d921 100644
--- a/build/Targets/Versions.props
+++ b/build/Targets/Versions.props
@@ -9,12 +9,13 @@
 
   <PropertyGroup>
     <!-- This is the assembly version of Roslyn from the .NET assembly perspective. It should only be revved during significant point releases. -->
-    <RoslynAssemblyVersionBase Condition="'$(RoslynAssemblyVersion)' == ''">2.3.0</RoslynAssemblyVersionBase>
+    <RoslynAssemblyVersionBase Condition="'$(RoslynAssemblyVersion)' == ''">2.6.0</RoslynAssemblyVersionBase>
     <!-- This is the file version of Roslyn, as placed in the PE header. It should be revved during point releases, and is also what provides the basis for our NuGet package versioning. -->
-    <RoslynFileVersionBase Condition="'$(RoslynFileVersionBase)' == ''">2.3.0</RoslynFileVersionBase>
+    <RoslynFileVersionBase Condition="'$(RoslynFileVersionBase)' == ''">2.6.0</RoslynFileVersionBase>
     <!-- The release moniker for our packages.  Developers should use "dev" and official builds pick the branch
          moniker listed below -->
     <RoslynNuGetMoniker Condition="'$(RoslynNuGetMoniker)' == ''">dev</RoslynNuGetMoniker>
+    <RoslynNuGetMoniker Condition="'$(OfficialBuild)' == 'true'">beta1</RoslynNuGetMoniker> 
     <!-- This is the base of the NuGet versioning for prerelease packages -->
     <NuGetPreReleaseVersion>$(RoslynFileVersionBase)-$(RoslynNuGetMoniker)</NuGetPreReleaseVersion>
 
-- 
GitLab