From d240ede0317485f4cd1b60ca2c5564db57910921 Mon Sep 17 00:00:00 2001 From: daothanhduy305 Date: Sat, 12 Sep 2026 17:59:32 +0700 Subject: [PATCH] Refresh the lock file for the SDK the runner installs CI restores with `--locked-mode`, and `setup-dotnet` is pinned only to `dotnet-version: '10'` with `dotnet-quality: 'ga'`, so it follows the latest 10.x GA. That SDK now brings Microsoft.AspNetCore.App.Internal.Assets 10.0.12 while the lock still pinned 10.0.10, and restore refused with NU1004. Nothing in the project changed; the implicit ASP.NET Core package moved under it. Regenerated with `scripts/dotnet-docker.sh restore --force-evaluate` so the value comes from the same SDK image the runner uses (10.0.401) rather than whatever happens to be installed locally. Verified with `--locked-mode` and the full suite, 346 tests, on that image. This will drift again on the next patch. The durable options are pinning the SDK exactly (global.json plus an exact `dotnet-version`) or dropping `--locked-mode`; leaving that decision alone for now. Co-Authored-By: Claude Opus 5 (1M context) --- CaddyManager/packages.lock.json | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/CaddyManager/packages.lock.json b/CaddyManager/packages.lock.json index 4ea7fd2..b03b10f 100644 --- a/CaddyManager/packages.lock.json +++ b/CaddyManager/packages.lock.json @@ -78,9 +78,9 @@ }, "Microsoft.AspNetCore.App.Internal.Assets": { "type": "Direct", - "requested": "[10.0.10, )", - "resolved": "10.0.10", - "contentHash": "8k0KoYKvNrSqP8E3oDJMBVKavlTEE6BacdLGtEDcxv9Hz0XxWFkD6JdLJsxXUlGeAfZ6YfvWmxKenl73qeCTSA==" + "requested": "[10.0.12, )", + "resolved": "10.0.12", + "contentHash": "+sIBo9AMBZH46qHWHQdfzcGMt+RuBaPYrUMOAM9VjA7MQ9QtIez3lq1C3E05+Yroa94KKt3DSWaxmCI4H28a9Q==" }, "Microsoft.AspNetCore.OpenApi": { "type": "Direct",