Update to .NET 10#20
Conversation
|
Warning Rate limit exceeded
To continue reviewing without waiting, purchase usage credits in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
OSPSuite.DataBinding, tests, starter) fromnet8.0-windowstonet10.0-windows.OSPSuite.Utilityreference from4.1.1.4→5.0.0.6(the .NET 10 build).3.0.1→4.0.0.actions/checkout@v6,actions/setup-dotnet@v5(10.x),actions/upload-artifact@v7. Dropmicrosoft/setup-msbuildand build withdotnet build/test/packto avoid the VS 2022 17.14 net10 warning. RecursivetestLogglob (./**/testLog*.html).permissions:blocks to both workflows (packages: write+contents: readon publish,packages: read+contents: readon PR build) to clear code-scanning warnings.Microsoft.CSharpPackageReference from the test project (NU1510 — pruned by net10).Test plan
dotnet buildclean (0 warnings, 0 errors)dotnet test— 53/53 passed locallydotnet packsucceeds; producedOSPSuite.DataBinding.4.0.0.nupkg4.0.0.xto GitHub PackagesFixes #19
Fixes #18