nuget cache setup

2026-09-13 17:46:15 +04:00
parent 68d15402ad
commit f72c90c6f2
6 changed files with 459 additions and 1 deletions
@@ -42,6 +42,13 @@ dotnet test --solution Just.PreciseMath.slnx -c Release --no-build
 dotnet format Just.PreciseMath.slnx --verify-no-changes --no-restore
 ```

+Commit each project's `packages.lock.json` with dependency changes. CI caches
+NuGet packages using those lock files and always runs `dotnet restore --locked-mode`,
+including on cache hits. After intentional dependency updates, run
+`dotnet restore --force-evaluate` and review the updated lock files before committing.
+Gitea's runner cache must be reachable from the job container, with persistent
+storage if the runner itself is recreated. No build outputs are cached.
+
 The initial smoke test checks that `DoubleDouble.One` exposes high and low
 components of `1.0` and `0.0`. It exercises the test/coverage pipeline, not the
 numerical accuracy of the planned library.