Convert v1.9 to v2.0 (#15938)

OrchardCMS · May 2, 2024 · c967b5d · c967b5d
1 parent 9c541cf
commit c967b5d
Show file tree

Hide file tree

Showing 4 changed files with 8 additions and 4 deletions.
diff --git a/mkdocs.yml b/mkdocs.yml
@@ -52,7 +52,7 @@ validation:
 # Add files here that are intentionally not in the navigation and thus omitted_files shouldn't warn about them.
 not_in_nav: |
   samples/
-  releases/1.9.0.md
+  releases/2.0.0.md
 
 # Extensions
 markdown_extensions:

diff --git a/src/OrchardCore.Build/OrchardCore.Commons.props b/src/OrchardCore.Build/OrchardCore.Commons.props
@@ -4,7 +4,7 @@
 
   <PropertyGroup>
     <LangVersion>12.0</LangVersion>
-    <VersionPrefix>1.9.0</VersionPrefix>
+    <VersionPrefix>2.0.0</VersionPrefix>
     <VersionSuffix>preview</VersionSuffix>
     <VersionSuffix Condition="'$(VersionSuffix)'!='' AND '$(BuildNumber)' != ''">$(VersionSuffix)-$(BuildNumber)</VersionSuffix>
     <WarningsNotAsErrors>612,618</WarningsNotAsErrors>

diff --git a/src/OrchardCore.Modules/OrchardCore.Email/Migrations/EmailMigrations.cs b/src/OrchardCore.Modules/OrchardCore.Email/Migrations/EmailMigrations.cs
@@ -16,7 +16,7 @@ public class EmailMigrations : DataMigration
     public int Create()
 #pragma warning restore CA1822
     {
-        // In version 1.9, the OrchardCore.Email.Smtp was split from OrchardCore.Email. To ensure we keep the change
+        // In version 2.0, the OrchardCore.Email.Smtp was split from OrchardCore.Email. To ensure we keep the change
         // backward compatible, we added this migration step to auto-enable the new SMTP feature for sites that use the
         // Email service and have SmtpSettings.
         ShellScope.AddDeferredTask(async scope =>

diff --git a/src/docs/releases/1.9.0.md → src/docs/releases/2.0.0.md b/src/docs/releases/1.9.0.md → src/docs/releases/2.0.0.md
@@ -1,7 +1,11 @@
-# Orchard Core 1.9.0
+# Orchard Core 2.0.0
 
 Release date: Not yet released
 
+## Upgrade Instructions
+
+Before upgrading to Orchard Core 2.0, you should first upgrade to 1.8, address any warnings, and only then upgrade to 2.0. Be sure to review the list of breaking changes documented below to ensure a seamless transition.
+
 ## Breaking Changes
 
 ### Drop `Newtonsoft.Json` Support