Skip to content

[release/10.0.1xx] Update dependencies from dotnet/dotnet#11218

Merged
jonathanpeppers merged 2 commits intorelease/10.0.1xxfrom
darc-release/10.0.1xx-843d7f23-2d2f-42ed-9b4c-d7fddacac03b
Apr 28, 2026
Merged

[release/10.0.1xx] Update dependencies from dotnet/dotnet#11218
jonathanpeppers merged 2 commits intorelease/10.0.1xxfrom
darc-release/10.0.1xx-843d7f23-2d2f-42ed-9b4c-d7fddacac03b

Conversation

@dotnet-maestro
Copy link
Copy Markdown
Contributor

This pull request updates the following dependencies

From https://github.com/dotnet/dotnet

…426.14

On relative base path root
Microsoft.DotNet.Build.Tasks.Feed From Version 10.0.0-beta.26216.121 -> To Version 10.0.0-beta.26226.114
Microsoft.NET.Sdk From Version 10.0.300-preview.0.26216.121 -> To Version 10.0.300-preview.0.26226.114
Microsoft.TemplateEngine.Authoring.Tasks From Version 10.0.300-preview.26216.121 -> To Version 10.0.300
The new .NET SDK (10.0.300-preview.0.26226.114) changed its internal
workload feature band from 10.0.300-preview.0 to 10.0.300. This caused
ConfigureLocalWorkload to place the android-deps workload manifest under
sdk-manifests/10.0.300-preview.0/ while the SDK looks in
sdk-manifests/10.0.300/, resulting in:

  Workload installation failed: Workload ID android-deps is not recognized.

Use $(VersionBand) (10.0.300) instead of $(DotNetPreviewVersionBand)
(10.0.300-preview.0) for DotNetSdkManifestsFolder.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@jonathanpeppers jonathanpeppers added the ready-to-review This PR is ready to review/merge, I think any CI failures are just flaky (ignorable). label Apr 28, 2026
@jonathanpeppers jonathanpeppers merged commit e2b9ec9 into release/10.0.1xx Apr 28, 2026
2 checks passed
@jonathanpeppers jonathanpeppers deleted the darc-release/10.0.1xx-843d7f23-2d2f-42ed-9b4c-d7fddacac03b branch April 28, 2026 15:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready-to-review This PR is ready to review/merge, I think any CI failures are just flaky (ignorable).

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants