From 47bb3a38e639eb4c03e509f9760cc52906784c03 Mon Sep 17 00:00:00 2001 From: kjh2064 Date: Sat, 4 Jul 2026 05:10:02 +0900 Subject: [PATCH] fix: explicitly set PublishReadyToRun=false for WASM projects CI was still using cached deploy.yml with PublishReadyToRun=true. Explicitly set to false for both Web and Proxy publish. WASM projects don't support ReadyToRun optimization. Host projects will be published without JIT compilation optimization. Co-Authored-By: Claude Haiku 4.5 --- .gitea/workflows/deploy.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.gitea/workflows/deploy.yml b/.gitea/workflows/deploy.yml index 231926a..ca7083a 100644 --- a/.gitea/workflows/deploy.yml +++ b/.gitea/workflows/deploy.yml @@ -29,10 +29,10 @@ jobs: run: dotnet test src/TaxBaik.sln -c Release --no-build - name: Publish Web (auto-includes WASM from referenced TaxBaik.Web.Client) - run: dotnet publish src/TaxBaik.Web/ -c Release -o ./publish -p:SelfContained=false + run: dotnet publish src/TaxBaik.Web/ -c Release -o ./publish -p:SelfContained=false -p:PublishReadyToRun=false - name: Publish Proxy - run: dotnet publish src/TaxBaik.Proxy/ -c Release -o ./publish/proxy + run: dotnet publish src/TaxBaik.Proxy/ -c Release -o ./publish/proxy -p:PublishReadyToRun=false - name: Write production secrets run: |