Prepare 1.2.0 development

.github/copilot-instructions.md

@@ -59,8 +59,8 @@ When a change affects public behavior, configuration, setup, or project guidance
 
 ### Changelog conventions
 
-- Changelog files are named after their version with no `v` prefix (for example `1.0.0.md`, `1.1.0.md`).
-- The next planned release is **1.1.0**. Document all upcoming changes — new features, fixes, dependency upgrades, branching or workflow changes, and other notable repository-level updates — in `src\CrestApps.Core.Docs\docs\changelog\1.1.0.md` until it ships.
+- Changelog files are named after their version with no `v` prefix (for example `1.1.0.md`, `1.2.0.md`).
+- The next planned release is **1.2.0**. Document all upcoming changes — new features, fixes, dependency upgrades, branching or workflow changes, and other notable repository-level updates — in `src\CrestApps.Core.Docs\docs\changelog\1.2.0.md` until it ships.
 - When a new development cycle begins, add a changelog file for that version (again with no `v` prefix), register it in `src\CrestApps.Core.Docs\sidebars.js` and `src\CrestApps.Core.Docs\docs\changelog\index.md`, and document ongoing work there.
 
 Keep the docs focused on `CrestApps.Core`. If you need to mention the Orchard Core implementation, treat it as a related downstream product and link to <https://orchardcore.crestapps.com>.

AGENTS.md

@@ -24,11 +24,11 @@ When a change affects public behavior, configuration, setup, or project guidance
 update the relevant docs under `src\CrestApps.Core.Docs\docs` and build the docs site.
 
 - Changelog files are named after their version with no `v` prefix (for example
-  `1.0.0.md`, `1.1.0.md`).
-- The next planned release is **1.1.0**. Document all upcoming changes going forward —
+  `1.1.0.md`, `1.2.0.md`).
+- The next planned release is **1.2.0**. Document all upcoming changes going forward —
   new features, fixes, dependency upgrades, branching or workflow changes, and other
   notable repository-level updates — in
-  `src\CrestApps.Core.Docs\docs\changelog\1.1.0.md` until it ships.
+  `src\CrestApps.Core.Docs\docs\changelog\1.2.0.md` until it ships.
 - When a new development cycle starts, add a changelog file for that version (again
   with no `v` prefix), register it in `src\CrestApps.Core.Docs\sidebars.js` and
   `src\CrestApps.Core.Docs\docs\changelog\index.md`, and document ongoing work there.

Directory.Build.props

@@ -45,7 +45,7 @@
   </ItemGroup>
 
   <PropertyGroup>
-    <VersionPrefix>1.1.0</VersionPrefix>
+    <VersionPrefix>1.2.0</VersionPrefix>
     <!-- VersionSuffixBase is the label passed in from the command line (e.g. "preview").
          VersionSuffix is assembled here so the build number is always appended when provided.
          Passing /p:VersionSuffix=... on the command line would create a global MSBuild property

Directory.Packages.props

@@ -27,7 +27,7 @@
     <PackageVersion Include="OllamaSharp" Version="5.4.30" />
     <PackageVersion Include="PdfPig" Version="0.1.15" />
     <PackageVersion Include="PDFsharp-MigraDoc" Version="6.2.4" />
-    <PackageVersion Include="SSH.NET" Version="2025.1.0" />
+    <PackageVersion Include="SSH.NET" Version="2026.0.0" />
     <PackageVersion Include="YesSql.Abstractions" Version="6.0.0" />
     <PackageVersion Include="YesSql.Core" Version="6.0.0" />
     <PackageVersion Include="YesSql.Provider.Sqlite" Version="6.0.0" />
@@ -93,4 +93,4 @@
     <PackageVersion Include="Microsoft.Data.Sqlite" Version="10.0.10" />
     <PackageVersion Include="SQLitePCLRaw.lib.e_sqlite3" Version="3.50.3" />
   </ItemGroup>
-</Project>
+</Project>

src/CrestApps.Core.Docs/docs/changelog/1.1.0.md

@@ -2,18 +2,16 @@
 sidebar_label: 1.1.0 Release Notes
 sidebar_position: 3
 title: "Version 1.1.0 Release Notes"
-description: Release notes for the upcoming CrestApps.Core 1.1.0 release.
+description: Release notes for the CrestApps.Core 1.1.0 release.
 ---
 
 # Version 1.1.0 Release Notes
 
 **Package version**: `1.1.0`
 
-:::info
-`CrestApps.Core` 1.1.0 is the next release and is currently in development. Nightly
-and preview builds are published from `main` under the `1.1.0` version prefix. This
-page will be updated as changes land after 1.0.0.
-:::
+**Release date**: 2026-08-13
+
+`CrestApps.Core` 1.1.0 was released on 2026-08-13.
 
 ## Highlights
 

src/CrestApps.Core.Docs/docs/changelog/1.2.0.md

@@ -0,0 +1,26 @@
+---
+sidebar_label: 1.2.0 Release Notes
+sidebar_position: 4
+title: "Version 1.2.0 Release Notes"
+description: Release notes for the upcoming CrestApps.Core 1.2.0 release.
+---
+
+# Version 1.2.0 Release Notes
+
+**Package version**: `1.2.0`
+
+:::info
+`CrestApps.Core` 1.2.0 is not yet released and is currently in development. Nightly
+and preview builds are published from `main` under the `1.2.0` version prefix. This
+page will be updated as changes land after 1.1.0.
+:::
+
+## Breaking Changes
+
+- None yet.
+
+## Change Logs
+
+- upgrades SSH.NET to 2026.0.0 to address the high-severity
+  [GHSA-q939-rpr3-3284](https://github.com/advisories/GHSA-q939-rpr3-3284)
+  advisory reported by NuGet audit

src/CrestApps.Core.Docs/docs/changelog/index.md

@@ -11,5 +11,6 @@ This section tracks `CrestApps.Core` releases and notable repository-level chang
 
 | Version | Highlights |
 | --- | --- |
-| [1.1.0](1.1.0) | Next release, currently in development (nightly and preview builds) |
+| [1.2.0](1.2.0) | Next release, currently in development (nightly and preview builds) |
+| [1.1.0](1.1.0) | Released 2026-08-13 with opt-in MCP server tool exposure, documentation search tool instances, and MCP/server fixes |
 | [1.0.0](1.0.0) | Initial standalone release plus merged configuration catalogs, automatic AI tool dependency expansion, clearer quick-start guidance, and deployment configuration diagnostics |

src/CrestApps.Core.Docs/sidebars.js

@@ -96,6 +96,7 @@ const sidebars = {
             label: 'Changelog',
             items: [
                 'changelog/index',
+                'changelog/1.2.0',
                 'changelog/1.1.0',
                 'changelog/1.0.0',
             ],