Skip to content

build(web): treat warnings as errors like every other project - #280

Merged
hoangsnowy merged 1 commit into
mainfrom
chore/web-warnings-as-errors
Oct 24, 2026
Merged

hoangsnowy merged 1 commit into
mainfrom
chore/web-warnings-as-errors

Conversation

@hoangsnowy

Copy link
Copy Markdown
Owner

Summary

  • AgentOs.Web.csproj set TreatWarningsAsErrors=false (since the 2026-05 naming refactor), so analyzer warnings piled up in the Web project while every other project enforced them through Directory.Build.props.
  • feat(autopilot): Autopilot is configured in Settings and waits out plan limits #279 cleared that backlog and the Web project now builds with 0 warnings, so this removes the opt-out to keep it that way.
  • The only remaining solution warning is the MSBuild ASPIRE010 from AppHost. That is the documented Aspire 13.5 hold in Directory.Packages.props: 13.6 needs the CLI-bundle migration. It is not a compiler warning.

Test plan

  • dotnet build AgentOs.slnx -c Release --no-incremental: 0 errors, 1 warning (ASPIRE010).
  • CI green.

🤖 Generated with Claude Code

https://claude.ai/code/session_018WAdQ7Rm24xss5QDSvXtJB

AgentOs.Web opted out of TreatWarningsAsErrors (since the 2026-05 rename), so analyzer
warnings piled up there while the rest of the solution enforced them. #279 cleared the
backlog; the Web project now builds with 0 warnings, so the opt-out goes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018WAdQ7Rm24xss5QDSvXtJB
@hoangsnowy
hoangsnowy merged commit 8ac2ae2 into main Oct 24, 2026
4 checks passed
@hoangsnowy
hoangsnowy deleted the chore/web-warnings-as-errors branch October 24, 2026 09:05
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.

1 participant