-
Notifications
You must be signed in to change notification settings - Fork 10.4k
[automated] Merge branch 'release/5.0' => 'master' #28295
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
Conversation
…otnet#28087) [release/5.0] Update dependencies from dotnet/efcore dotnet/runtime - Merge branch 'release/5.0' into darc-release/5.0-d4478e43-6d04-47a1-8a7c-c6c2dcd90d64 - Tweak tests - Remove Extensions.Internal.Transport from Runtime - Microsoft.AspNetCore.App.Runtime project does not expect compilation-only references - !fixup! Rearrange a `Condition` - slight change to 49cc13c workaround - Do not compile against assemblies with newer assembly versions - avoid problems with e.g. System.Extensions.DependencyInjection in 5.0.1 - Revert "Remove package version pinning for ref/ assemblies in servicing (dotnet#25851)" - dotnet/runtime assembly versions are unexpectedly changing in servicing This reverts commit bfc1ec6. - Update `SharedFxTests` to handle dotnet/runtime version changes - assemblies with non-0.0 versions end up in Microsoft.AspNetCore.App - future-proofs these tests because more dotnet/runtime versions may change - !fixup! Revert of bfc1ec6 messed up `RepoTasks` - need the RTM-versioned packages on all platforms - we only target `net472` on Windows
…125.9 (dotnet#28260) [release/5.0] Update dependencies from dotnet/efcore
Description We introduced a public property as part of dotnet#27907 to enable users to opt-in. Turns out that this caused issues since we didn't update the target pack. As a result, the Razor compiler treats this new property as a regular HTML attribute (of type string) instead of as a boolean. In turn this causes the template to error at runtime when the application starts. Customer Impact Customers using 5.0.1 won't be able to create and run new blazor apps out of the box. They can fix the template code by preceding the true value in the attribute with @ to force the compiler to interpret it as C#. (Which is the same fix we are applying). Regression? Yes, 5.0.0. Users were able to create new blazor templates without this issue. Risk Low. We've manually validated the fix against a new project from a 5.0.1 template.
43d3389
to
fc93e59
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Auto-approving branch merge.
Hello @msftbot[bot]! Because this pull request has the Do note that I've been instructed to only help merge pull requests of this repository that have been opened for at least 60 minutes. No worries though, I will be back when the time is right! 😉 p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
- The test doesn't appear to handle or expect prerelease tags
@dougbu It looks like the changes you made to SharedFrameworkAssembliesHaveExpectedAssemblyVersions when merging a dependency update here didn't take into account package versions with prerelease tags. I modified the test to strip the prerelease tag before calling Version.Parse. I hope that's OK! index 8aa8a8bffe..1a205b958f 100644
--- a/src/Framework/test/SharedFxTests.cs
+++ b/src/Framework/test/SharedFxTests.cs
@@ -171,7 +171,8 @@ namespace Microsoft.AspNetCore
.Split(';', StringSplitOptions.RemoveEmptyEntries)
.ToHashSet();
- var version = Version.Parse(TestData.GetMicrosoftNETCoreAppPackageVersion());
+ var versionStringWithoutPrereleaseTag = TestData.GetMicrosoftNETCoreAppPackageVersion().Split('-', 2)[0];
+ var version = Version.Parse(versionStringWithoutPrereleaseTag);
var dlls = Directory.GetFiles(_sharedFxRoot, "*.dll", SearchOption.AllDirectories);
Assert.NotEmpty(dlls);
|
Perfect❕ |
I detected changes in the release/5.0 branch which have not been merged yet to master. I'm a robot and am configured to help you automatically keep master up to date, so I've opened this PR.
This PR merges commits made on release/5.0 by the following committers:
Instructions for merging from UI
This PR will not be auto-merged. When pull request checks pass, complete this PR by creating a merge commit, not a squash or rebase commit.
If this repo does not allow creating merge commits from the GitHub UI, use command line instructions.
Instructions for merging via command line
Run these commands to merge this pull request from the command line.
or if you are using SSH
After PR checks are complete push the branch
Instructions for resolving conflicts
Instructions for updating this pull request
Contributors to this repo have permission update this pull request by pushing to the branch 'merge/release/5.0-to-master'. This can be done to resolve conflicts or make other changes to this pull request before it is merged.
or if you are using SSH
Contact .NET Core Engineering if you have questions or issues.
Also, if this PR was generated incorrectly, help us fix it. See https://github.com/dotnet/arcade/blob/master/scripts/GitHubMergeBranches.ps1.