case 4690 - version bump and confirmation of choices for net10-port

dev-raven.bat

@@ -3,7 +3,7 @@
 @echo **************************************************************
 cd C:\data\code\raven
 call code .
-cd C:\data\code\raven-client\ayanova
+cd C:\data\code\raven-client
 call code .
 start cmd /k Call C:\data\code\raven-client\ayanova\appdev.bat
 start cmd /k Call C:\data\code\raven\startsql.bat

devdocs/modernization/NET10-PORT.md

@@ -9,7 +9,7 @@ under "Deferred", not into the branch.
 | Starting point | AyaNova 8.2.4: ASP.NET Core 8, EF Core 8 |
 | Target | `net10.0`, every back-end package at its current release |
 | Front end | Minimal or no change. Rebuild only if needed (open question) |
-| Branch | `net10-port` in `raven` (and `raven-client` only if the client changes) |
+| Branch | `net10-port` in `raven` (and `raven-client` and `raven-test-integration` and `raven-launcher`) |
 | Baseline tag | `net8-baseline`, on the last commit before the port |
 | Release version | Not yet decided (open question) |
 
@@ -104,7 +104,7 @@ them. Items touching those three areas carry more weight here than they did in S
 
 These are bugs, not port mechanics, so each is a separate commit that can be reverted alone.
 Sockeye included its equivalents in the port branch. John decides per item whether they go
-in this branch or a follow-up release.
+in this branch or a follow-up release. UPDATE: John has decided these all go in this branch and some more additional cases in the case database that are urgent, exact cases TBD.
 
 - [ ] **Case 4676: data-list SQL injection — priority.** The numeric and role filters in `DataListSqlFilterCriteriaBuilder` built SQL from input. In AyaNova any authenticated user who can open a data list could reach them. Port the Sockeye fix
 - [ ] **`DbUtil.AdminConnectionString`.** If it is `_dbConnectionString.Replace(_dbName, "postgres")`, any customer whose role name, password or host contains the database name as text gets a mangled admin connection, and the boot check authenticates as the wrong user. Fix: `new NpgsqlConnectionStringBuilder(cs) { Database = "postgres" }.ConnectionString`
@@ -159,10 +159,10 @@ suite is waiting on (case 4653, case 4654, the contract issue).
 
 ## Open questions
 
-- Release version number (Sockeye's port was released as 8.1.0)
+- Release version number (Sockeye's port was released as 8.1.0) Answer: 8.3.0 will be the version
-- `raven-launcher` (.NET 8, self-contained): move to .NET 10 in the same release?
+- `raven-launcher` (.NET 8, self-contained): move to .NET 10 in the same release? Answer: Yes
-- `raven-test-integration`: move to `net10.0` (separate commit) or leave on `net8.0`? It only talks HTTP to the server
+- `raven-test-integration`: move to `net10.0` (separate commit) or leave on `net8.0`? It only talks HTTP to the server Answer: Move to net10.0 for consistency
-- Does the client need a rebuild in this pass, or can its current output be carried across?
+- Does the client need a rebuild in this pass, or can its current output be carried across? Answer: yes it will have minor changes as well as version number to 8.3.0
 - Section 3: which fixes go in this branch, which in a follow-up
 - How the .NET 10 runtime gets onto Ubuntu 24.04 hosts
 

dist/install/windows/x64/lan.iss

@@ -1,7 +1,7 @@
 ; LAN install for internal network use only     
 
 #define MyAppName "AyaNova server"
-#define MyAppVersion "8.2.4"
+#define MyAppVersion "8.3.0"
 #define MyAppPublisher "Ground Zero Tech-Works, Inc."
 #define MyAppURL "https://ayanova.com/"
 #define MyAppLauncherExeName "ayanova-launcher.exe"

dist/install/windows/x64/standalone.iss

@@ -3,7 +3,7 @@
 ; external to lan requires different config      
 
 #define MyAppName "AyaNova"
-#define MyAppVersion "8.2.4"
+#define MyAppVersion "8.3.0"
 #define MyAppPublisher "Ground Zero Tech-Works, Inc."
 #define MyAppURL "https://ayanova.com/"
 #define MyAppLauncherExeName "ayanova-launcher.exe"

dist/latest-version.json

@@ -1,4 +1,4 @@
 {
-    "latestversion":"8.2.4",
+    "latestversion":"8.3.0",
-    "changelogurl":"https://ayanova.com/docs/changelog/#ayanova-823"
+    "changelogurl":"https://ayanova.com/docs/changelog/#ayanova-830"
 }

docs/8.0/ayanova/docs/acc-service-rates.md

@@ -47,7 +47,7 @@ Service rates Cost and Price fields are **locked** to prevent editing once they
 
 ### Retiring
 
-When a rate is retired it should be set to inactive by un-checking it's Active checkbox and a new rate created to take it's place. Rate names must be unique so for example if a rate changes yearly then the old rate might be called "In-shop service 2024" and the new rate called "In shop service 2025" to ensure names are unique and recognized by users.
+When a rate is retired it should be set to inactive by un-checking it's Active checkbox and a new rate created to take it's place. Rate names must be unique so for example if a rate changes yearly then the old rate might be called "In-shop service 2024" and the new rate called "In shop service 2026" to ensure names are unique and recognized by users.
 
 ### Contract service rates
 

docs/8.0/ayanova/docs/ay-about.md

@@ -20,7 +20,7 @@ This section provides information regarding the AyaNova web app client running i
 
 #### Version
 
-This is the version number of the AyaNova web application. When a new version of AyaNova is released this number will go up. AyaNova uses the industry standard [semantic versioning system](https://semver.org/) which is 3 numbers separated by periods for example `8.2.4`.
+This is the version number of the AyaNova web application. When a new version of AyaNova is released this number will go up. AyaNova uses the industry standard [semantic versioning system](https://semver.org/) which is 3 numbers separated by periods for example `8.3.0`.
 
 The leftmost number, for example **8**.1.2 is the major release version indicating major changes to the program that are not backwards compatible to the prior major release version.
 

docs/8.0/ayanova/docs/changelog.md

@@ -6,6 +6,13 @@ If you are viewing this page from your local copy of AyaNova be advised that it
 
 See the [upgrade instructions](ops-upgrade.md) section of this manual for details.
 
+## 2026
+
+### AyaNova 8.3.0
+
+IN PROGRESS
+
+
 ## 2025
 
 ### AyaNova 8.2.4

docs/8.0/ayanova/mkdocs.yml

@@ -8,7 +8,7 @@ site_name: AyaNova manual
 site_dir: "../../../server/AyaNova/wwwroot/docs"
 site_url: https://ayanova.com/docs/
 strict: true
-copyright: Copyright © 2022-2025 Ground Zero Tech-Works Inc. REV-2025-11-24
+copyright: Copyright © 2022-2026 Ground Zero Tech-Works Inc. REV-2026-10-22
 extra:
   generator: false
 # Extensions

server/AyaNova/AyaNova.csproj

@@ -4,8 +4,8 @@
   </PropertyGroup>
   <PropertyGroup>
     <GenerateFullPaths>true</GenerateFullPaths>    
-    <Version>8.2.4</Version>
+    <Version>8.3.0</Version>
-    <FileVersion>8.2.4.0</FileVersion>
+    <FileVersion>8.3.0.0</FileVersion>
     <ApplicationIcon>ayanova.ico</ApplicationIcon>
     <DocumentationFile>bin\$(Configuration)\$(TargetFramework)\$(AssemblyName).xml</DocumentationFile>
     <noWarn>1591</noWarn>

server/AyaNova/util/AyaNovaVersion.cs

@@ -5,7 +5,7 @@ namespace AyaNova.Util
     /// </summary>
     internal static class AyaNovaVersion
     {
-        public const string VersionString = "8.2.4";
+        public const string VersionString = "8.3.0";
         public const string FullNameAndVersion = "AyaNova server " + VersionString;
         public const string CurrentApiVersion="v8";
     }//eoc