build(deps): bump dotnet-sdk from 10.0.300 to 10.0.301#5322
Conversation
Bumps [dotnet-sdk](https://github.com/dotnet/sdk) from 10.0.300 to 10.0.301. - [Release notes](https://github.com/dotnet/sdk/releases) - [Commits](dotnet/sdk@v10.0.300...v10.0.301) --- updated-dependencies: - dependency-name: dotnet-sdk dependency-version: 10.0.301 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
The 10.0.301 workload's Microsoft.iOS only accepts iOS TargetPlatformVersion 26.0 or 26.5 (dropping 26.2). CI pinned Xcode 26.3 on macos-15, whose iOS SDK is 26.2, so net10.0-ios builds failed with NETSDK1140. macos-26 ships Xcode 26.5 (iOS 26.5 SDK + simulator), which the new workload supports. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: James Crosswell <james.crosswell@gmail.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #5322 +/- ##
==========================================
+ Coverage 74.15% 74.16% +0.01%
==========================================
Files 508 508
Lines 18353 18353
Branches 3586 3586
==========================================
+ Hits 13610 13612 +2
+ Misses 3870 3869 -1
+ Partials 873 872 -1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
The MAUI device/integration test apps explicitly pin the iOS TargetPlatformVersion to 26.2, which overrides the SDK default regardless of the selected Xcode. The 10.0.301 workload only accepts 26.0/26.5, so these pins still produced NETSDK1140 even after moving to Xcode 26.5. Update the pins (and matching comments) to 26.5. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: James Crosswell <james.crosswell@gmail.com>
There was a problem hiding this comment.
@Flash0ver .NET 10.0.301 requires XCode 26.5 which is only available on the macos-26 runners so I had to bump both in order to get this PR working.
We don't lose much in doing this (we were already unable to run any tests against the net9.0-ios targets in CI when we were running XCode 26.3)... so I can't see any reason not to do it. It's just the logical conclusion of our decision to targe the most recent version of .NET (especially for the mobile integrations).
jamescrosswell
left a comment
There was a problem hiding this comment.
Automated approval: dependency update, CI green, no breaking changes in description.
Bumps dotnet-sdk from 10.0.300 to 10.0.301.
Release notes
Sourced from dotnet-sdk's releases.
... (truncated)
Commits
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)