Skip to content

Fix docs deploy: disable AOT on Playground.Wasm#32

Merged
koenbeuk merged 1 commit intomainfrom
fix/docs-deploy-aot
Apr 13, 2026
Merged

Fix docs deploy: disable AOT on Playground.Wasm#32
koenbeuk merged 1 commit intomainfrom
fix/docs-deploy-aot

Conversation

@koenbeuk
Copy link
Copy Markdown
Collaborator

Summary

  • PR Enhance documentation workflow and add Blazor WASM playground support #30 broke the docs deploy. Publish step fails with: error : AOT is not supported without IL trimming (PublishTrimmed=true required).
  • Root cause: .NET 10's `wasm-tools` workload tightened its check — `RunAOTCompilation=true` now requires `PublishTrimmed=true`. The playground can't enable trimming (Roslyn + EF Core don't trim cleanly), so AOT has to go.
  • Trade-off: the playground runs interpreted instead of AOT'd. Roslyn startup is slower, but the build works. AOT was a nice-to-have, not a correctness requirement.
  • Also drops `dotnet workload install wasm-tools` from all 4 workflows — without AOT, no emscripten/wasm-opt invocation happens, saving ~30-60s per run.

Test plan

  • `dotnet publish src/Docs/Playground.Wasm -c Release` succeeds locally
  • No emscripten/wasm-opt/relink steps invoked (verified with `-v normal`)
  • After merge, Deploy Docs workflow goes green and publishes to gh-pages

🤖 Generated with Claude Code

.NET 10's wasm-tools workload rejects RunAOTCompilation when
PublishTrimmed is false, which broke the Publish step in docs.yml:

  error : AOT is not supported without IL trimming (PublishTrimmed=true required).

We can't enable trimming because Roslyn + EF Core don't trim cleanly,
so disable AOT instead — the playground runs interpreted, trading
Roslyn startup speed for a working build. Also drops the wasm-tools
workload install from all 4 workflows; without AOT nothing in the
publish path invokes emscripten / wasm-opt.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings April 13, 2026 02:12
@koenbeuk
Copy link
Copy Markdown
Collaborator Author

worth it for now

@koenbeuk koenbeuk closed this Apr 13, 2026
@koenbeuk koenbeuk merged commit 4f0c526 into main Apr 13, 2026
10 checks passed
@koenbeuk koenbeuk deleted the fix/docs-deploy-aot branch April 13, 2026 02:13
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR fixes the docs deployment pipeline by disabling WebAssembly AOT compilation for the Blazor playground project (since .NET 10’s wasm-tools now requires trimming for AOT, and trimming can’t be enabled for this app). It also removes unnecessary wasm-tools workload installation steps from GitHub Actions workflows to speed up CI.

Changes:

  • Disable WASM AOT for Playground.Wasm by removing RunAOTCompilation and documenting why trimming/AOT are off.
  • Remove dotnet workload install wasm-tools from CI, docs deploy, release, and benchmarks workflows.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.

Show a summary per file
File Description
src/Docs/Playground.Wasm/ExpressiveSharp.Docs.Playground.Wasm.csproj Removes AOT and updates trimming/AOT rationale to keep publishing working under .NET 10.
.github/workflows/release.yml Drops wasm-tools workload install step (no longer needed without AOT).
.github/workflows/docs.yml Drops wasm-tools workload install step before publishing the playground.
.github/workflows/ci.yml Drops wasm-tools workload install step from the main CI job.
.github/workflows/benchmarks.yml Drops wasm-tools workload install step from benchmark runs.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@codecov
Copy link
Copy Markdown

codecov bot commented Apr 13, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants