Allow for publishing to nugettest.org

.github/workflows/publish.yml

@@ -1,4 +1,4 @@
-name: Publish Nuget Package
+name: Publish Release Package
 on:
   push:
     branches:

.github/workflows/staging.yml

@@ -0,0 +1,24 @@
+name: Publish Testing Package
+on:
+  push:
+    branches:
+      - "staging/**"
+jobs:
+  publish:
+    name: Package Release
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - name: Setup dotnet
+        uses: actions/setup-dotnet@v1
+        with:
+          dotnet-version: "6.0.x"
+      - name: Install dependencies
+        run: dotnet restore
+      - name: Package
+        run: dotnet pack --no-restore -o .
+      - name: Publish to Nuget
+        env:
+          NUGET_KEY: ${{ secrets.DEPLOY_TEST_KEY }}
+          NUGET_API: https://apiint.nugettest.org/v3/index.json
+        run: dotnet nuget push CSTNet.*.nupkg --api-key $NUGET_KEY --source $NUGET_API

CSTNet/CSTNet.csproj

@@ -1,7 +1,7 @@
 <Project Sdk="Microsoft.NET.Sdk">
 
     <PropertyGroup>
-        <TargetFrameworks>netstandard2.1;net6.0</TargetFrameworks>
+        <TargetFrameworks>net6.0</TargetFrameworks>
         <Version>2.0.100-beta2</Version>
         <Nullable>enable</Nullable>
         <LangVersion>latest</LangVersion>

changelog.md

@@ -4,16 +4,18 @@
 
 This version supports both .NET Standard 2.1 and .NET 6 and brings with it (much needed) quality of life changes internally. Apart from that, nothing has changed to the API itself apart from much needed documentation.
 
-### New Release Cycle
-
-Because this library has no third-party dependencies, CST.NET's release cycle will generally follow .NET's LTS cycle. This is why .NET 5 was skipped. Minor releases will consist of targeting latest LTS. For example, 2.1 will drop Standard 2.1 (ironically) in favor of .NET 8.0, 6.0 will continue to be targeted until it's end of life and 2.2 will strictly target 8.0. This should ensure continues security updates and Enterprise-grade support.
-
 ### UIText class and interface
 
 Based on FreeSO's API, the ``UIText`` class allows for traversing in ``/<directory>/<language>.dir`` directories and searching CST files by their Id number. (e.g. _*154*_miscstrings.cst). By defualt, the base path is ``/<program directory>/uitext/<language>.dir``. You may also create your own implementation based on these APIs using the ``IUIText`` interface which mine also uses.
 
 For more info, see [usage.md](./usage.md).
 
+### New Release Cycle
+
+Because this library has no third-party dependencies, CST.NET's release cycle will generally follow .NET's LTS cycle. This is why .NET 5 was skipped. Minor releases will consist of targeting latest LTS.
+
+For example, 2.5 adds .NET 8.0 next to 6.0 until the latter reaches end of life and finally 2.6 targets only 8.0. Keep in mind, this is all just hypothetical. Realistically, this could happen as soon as 2.2 because parameters will land as earlier as 2.1.
+
 ## 1.0.300
 
 - Minor patch.