Skip to content

fix: resolve package compatibility and MudBlazor v9 breaking changes#116

Merged
phmatray merged 1 commit intomainfrom
develop
Mar 5, 2026
Merged

fix: resolve package compatibility and MudBlazor v9 breaking changes#116
phmatray merged 1 commit intomainfrom
develop

Conversation

@phmatray
Copy link
Owner

@phmatray phmatray commented Mar 5, 2026

Summary

  • Fix Renovate bot error: Directory.Packages.props was using 10.0.3 Microsoft packages for all TFMs, but those only support net10.0. Now uses 8.0.x for net8.0, 9.0.x for net9.0, and 10.0.3 for net10.0.
  • Migrate to MudBlazor v9 API: ActivatorContentCustomContent, InputStyleInputClass, PanelClass moved from MudTabs to MudTabPanel, ServerData delegate now requires CancellationToken.
  • Fix test compilation: Replace removed SetText() with ValueChanged.InvokeAsync(), suppress MUD0012 analyzer in test projects.

Test plan

  • dotnet build succeeds with 0 errors across all TFMs (net8.0, net9.0, net10.0)
  • dotnet test passes 666/668 tests (1 pre-existing failure unrelated to this PR, 1 skipped)
  • CI pipeline passes on GitHub Actions

🤖 Generated with Claude Code

- Fix Directory.Packages.props: use TFM-appropriate Microsoft package
  versions (8.0.x for net8.0, 9.0.x for net9.0, 10.0.x for net10.0)
  instead of 10.0.3 across all targets (Renovate bot error)
- Migrate MudFileUpload ActivatorContent to CustomContent (MudBlazor v9)
- Remove obsolete InputStyle, move opacity to InputClass
- Update ServerDataFunc signature with CancellationToken parameter
- Move PanelClass from MudTabs to MudTabPanel (MudBlazor v9 API change)
- Replace removed SetText() with ValueChanged.InvokeAsync() in tests
- Suppress MUD0012 analyzer in test projects for .Value assertions

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@phmatray phmatray merged commit eedd854 into main Mar 5, 2026
0 of 3 checks passed
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