-
Notifications
You must be signed in to change notification settings - Fork 10.4k
[blazor-wasm] Update dependencies from dotnet/arcade aspnet/Blazor #17307
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[blazor-wasm] Update dependencies from dotnet/arcade aspnet/Blazor #17307
Conversation
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
@JunTaoLuo, looks like things are failing to resolve the correct version. Are you the person to look into this? |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
…121.2 - Microsoft.AspNetCore.Blazor.Mono - 3.1.0-preview4.19571.2
90ec253
to
601f2a2
Compare
…126.1 - Microsoft.AspNetCore.Blazor.Mono - 3.1.0-preview4.19576.1
@pranavkm looks like similar errors. <3 |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
…126.2 - Microsoft.AspNetCore.Blazor.Mono - 3.1.0-preview4.19576.2
There was something causing the builds to hang, i looked at the dumps and seems to be something on the components E2E. I will be investigating further shortly. Now it seems its failing to restore some packages. |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
Seems like the feed with stable versions has been deleted in the updated. I've re-added it and that should fix the existing restore issues.
I've cherry-picked a commit from @pranavkm that contains the updates we need in blazor-wasm to take in the new mono drop and that was causing the build hangs (due to massive test failures). |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
@javiercn thanks, was just about to do that. |
Auto-Merge StatusThis pull request has been merged because the following merge policies have succeeded.
|
This pull request updates the following dependencies
From https://github.com/aspnet/Blazor
From https://github.com/aspnet/AspNetCore-Tooling
From https://github.com/aspnet/EntityFrameworkCore
Coherency Updates
The following updates ensure that dependencies with a CoherentParentDependency
attribute were produced in a build used as input to the parent dependency's build.
See Dependency Description Format
From https://github.com/dotnet/arcade