Removed Versioning lib

PsModules/CommonBuild/Public/Show-FullBuildInfo.ps1

@@ -31,6 +31,4 @@ function Show-FullBuildInfo
 
     Write-Verbose ".NET SDKs:"
     Write-Verbose (dotnet --list-sdks | Out-String)
-    Write-Verbose "GITHUB vars"
-    Write-Verbose (dir env:GITHUB* | Format-Table -Property Name, value | Out-String)
 }

docfx/docfx.json

@@ -1,18 +1,5 @@
 {
     "$schema": "https://raw.githubusercontent.com/dotnet/docfx/main/schemas/docfx.schema.json",
-    "metadata": [
-        {
-            "memberLayout":"separatePages",
-            "namespaceLayout":"nested",
-            "src": [
-                {
-                    "src": "../src/Ubiquity.NET.Versioning",
-                    "files": ["**.csproj"]
-                }
-            ],
-            "dest": "versioning-lib/api"
-        }
-    ],
     "build": {
         // xref YAML files that contain mappings from an XREF ID to the actual URL for the content in an external source
         "xref": [
@@ -28,17 +15,6 @@
                     "toc.yml"
                 ]
             },
-            {
-                // Versioning project additional content, Includes the generated metadata API folder
-                "files": [
-                    "versioning-lib/**.{md,yml}"
-                ],
-                // Exclude the namespace overwrites and XREF maps as they are listed explicitly elsewhere
-                "exclude": [
-                    "**/namespaces/**.md",
-                    "**/*-xref.yml"
-                ]
-            },
             {
                 // Build tasks project additional content
                 // There is no API generated for this, it's just consumable for the build tasks.

docfx/documentation.msbuildproj

@@ -24,7 +24,6 @@
     <!--Everything in the versioning-lib sub-folder except the API folder as that contains generated files -->
     <None Include="versioning-lib/**" Exclude="versioning-lib/api/**" />
     <!-- Explicitly call out the non-generated files in the API folder-->
-    <None Include="versioning-lib/api/.gitignore" />
   </ItemGroup>
   <ItemGroup>
     <!--Everything in the build-tasks sub-folder except the API folder as that contains generated files -->

docfx/index.md

@@ -1,27 +1,27 @@
-# Ubiquity.NET.Versioning
-`Ubiquity.NET.Versioning*` family of libraries provides support for a number of scenarios
-but the primary focus is automated build versioning that embraces the principal of least surprise
-while conforming to the syntax of CSemVer and CSemVer-CI
+# Ubiquity.NET.Versioning.Tasks
+`Ubiquity.NET.Versioning.Tasks` library provides support for automated build scenarios
+with the primary focus is automated build versioning that embraces the principal of
+least surprise while conforming to the syntax of CSemVer and CSemVer-CI for versioning.
 
 ## The Libraries in this repository
 
 | Library | Description |
 |---------|-------------|
-| [Ubiquity.NET.Versioning](versioning-lib/index.md) | This library contains support for use of CSemVer at runtime |
 | [Ubiquity.NET.Versioning.Build.Tasks](build-tasks/index.md) | This library contains support for automated versioning at BUILD time |
 
 >[!IMPORTANT]
 > There is confusion on the ordering of a CI build with relation to a release build with
 > CSemVer-CI. A CI Build is either an initial build of an unreleased version with
 > [Major.Minor.Patch] == [0.0.0]. Or, it is based on the previously released version and
 > is [Major.Minor.Patch+1]. That is, a CI build is ordered ***BEFORE*** all release builds,
-> or it is ordered ***AFTER*** the ***specific*** release it is based on! In particular a
-> CI build version does ***NOT*** indicate what it will become when it is finally released,
-> but what release it was based on (If any). To simplify that, for clarity, a CI build
-> contains everything in the release it was based on and additional changes (that might
-> remove things). CI builds are, by definition NOT stable and consumers cannot rely on
-> them for predictions of future stability. A given CI build may even represent an
-> abandoned approach that never becomes a release!
+> or it is ordered ***AFTER*** the ***specific*** release it is based on!
+>
+> In particular a CI build version does ***NOT*** indicate what it will become when it is
+> finally released/ It ONLY indicates what release it was based on (If any). To simplify
+> that, for clarity, a CI build contains everything in the release it was based on and
+> additional changes (that might remove things). CI builds are, by definition NOT stable
+> and consumers cannot rely on them for predictions of future stability. A given CI build
+> may even represent an abandoned approach that never becomes a release!
 
 ---
 [Attributions](Attributions.md)

docfx/toc.yml

@@ -9,7 +9,5 @@
   href: https://github.com/UbiquityDotNET/CSemVer.GitBuild
 - name: Projects
   items:
-    - name: Ubiquity.NET.Versioning
-      href: versioning-lib/index.md
     - name: Ubiquity.NET.Versioning.Build.Tasks
       href: build-tasks/index.md