Skip to content
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

jbrelease/6.0 #1

Open
wants to merge 183 commits into
base: release/6.0
Choose a base branch
from
Open

jbrelease/6.0 #1

wants to merge 183 commits into from

Conversation

jb-preston-jennings
Copy link
Collaborator

No description provided.

vseanreesermsft and others added 30 commits June 18, 2023 19:23
Merge from public release/6.0 to internal/release/6.0 and resolve conflicts if necessary
Merge from public release/6.0 to internal/release/6.0 and resolve conflicts if necessary
Forcibly close socket when connection is aborted.
refs VINYL-14964
refs VINYL-14964
refs VINYL-14964
refs VINYL-14964
wtgodbe and others added 30 commits November 14, 2023 14:24
….0-2023-11-14-1024

Merging internal commits for release/6.0
…017.3 (dotnet#52226)

[release/6.0] Update dependencies from dotnet/arcade
…otnet-efcore build 20231120.13

dotnet-ef , Microsoft.EntityFrameworkCore , Microsoft.EntityFrameworkCore.Design , Microsoft.EntityFrameworkCore.InMemory , Microsoft.EntityFrameworkCore.Relational , Microsoft.EntityFrameworkCore.Sqlite , Microsoft.EntityFrameworkCore.SqlServer , Microsoft.EntityFrameworkCore.Tools
 From Version 6.0.26 -> To Version 6.0.26
…ng/internal/dotnet-efcore

This pull request updates the following dependencies

[marker]: <> (Begin:1ac68a20-28fc-4e11-3a4d-08d961c5a689)
## From https://dev.azure.com/dnceng/internal/_git/dotnet-efcore
- **Subscription**: 1ac68a20-28fc-4e11-3a4d-08d961c5a689
- **Build**: 20231120.13
- **Date Produced**: November 20, 2023 9:09:18 PM UTC
- **Commit**: b254074a09b0021d472383ea15b3bb703eae3ee3
- **Branch**: refs/heads/internal/release/6.0

[DependencyUpdate]: <> (Begin)

- **Updates**:
  - **dotnet-ef**: [from 6.0.26 to 6.0.26][1]
  - **Microsoft.EntityFrameworkCore**: [from 6.0.26 to 6.0.26][1]
  - **Microsoft.EntityFrameworkCore.Design**: [from 6.0.26 to 6.0.26][1]
  - **Microsoft.EntityFrameworkCore.InMemory**: [from 6.0.26 to 6.0.26][1]
  - **Microsoft.EntityFrameworkCore.Relational**: [from 6.0.26 to 6.0.26][1]
  - **Microsoft.EntityFrameworkCore.Sqlite**: [from 6.0.26 to 6.0.26][1]
  - **Microsoft.EntityFrameworkCore.SqlServer**: [from 6.0.26 to 6.0.26][1]
  - **Microsoft.EntityFrameworkCore.Tools**: [from 6.0.26 to 6.0.26][1]

[1]: https://dev.azure.com/dnceng/internal/_git/dotnet-efcore/branches?baseVersion=GC6eb9da7723&targetVersion=GCb254074a09&_a=files

[DependencyUpdate]: <> (End)

[marker]: <> (End:1ac68a20-28fc-4e11-3a4d-08d961c5a689)
…otnet-runtime build 20231120.14

Microsoft.Internal.Runtime.AspNetCore.Transport , Microsoft.NET.Runtime.MonoAOTCompiler.Task , Microsoft.NET.Runtime.WebAssembly.Sdk , Microsoft.NETCore.App.Ref , Microsoft.NETCore.App.Runtime.AOT.win-x64.Cross.browser-wasm , Microsoft.NETCore.App.Runtime.win-x64 , Microsoft.NETCore.BrowserDebugHost.Transport
 From Version 6.0.26-servicing.23565.9 -> To Version 6.0.26-servicing.23570.14
…ng/internal/dotnet-runtime

This pull request updates the following dependencies

[marker]: <> (Begin:7745f62d-e15b-4ba3-39b3-08d960f4ca81)
## From https://dev.azure.com/dnceng/internal/_git/dotnet-runtime
- **Subscription**: 7745f62d-e15b-4ba3-39b3-08d960f4ca81
- **Build**: 20231120.14
- **Date Produced**: November 20, 2023 10:20:49 PM UTC
- **Commit**: 88c49c921704ba9cc603f167fc09fa2a79cebb63
- **Branch**: refs/heads/internal/release/6.0

[DependencyUpdate]: <> (Begin)

- **Updates**:
  - **Microsoft.Internal.Runtime.AspNetCore.Transport**: [from 6.0.26-servicing.23565.9 to 6.0.26-servicing.23570.14][1]
  - **Microsoft.NET.Runtime.MonoAOTCompiler.Task**: [from 6.0.26 to 6.0.26][1]
  - **Microsoft.NET.Runtime.WebAssembly.Sdk**: [from 6.0.26 to 6.0.26][1]
  - **Microsoft.NETCore.App.Ref**: [from 6.0.26 to 6.0.26][1]
  - **Microsoft.NETCore.App.Runtime.AOT.win-x64.Cross.browser-wasm**: [from 6.0.26 to 6.0.26][1]
  - **Microsoft.NETCore.App.Runtime.win-x64**: [from 6.0.26 to 6.0.26][1]
  - **Microsoft.NETCore.BrowserDebugHost.Transport**: [from 6.0.26-servicing.23565.9 to 6.0.26-servicing.23570.14][1]

[1]: https://dev.azure.com/dnceng/internal/_git/dotnet-runtime/branches?baseVersion=GCf1697b9e74&targetVersion=GC88c49c9217&_a=files

[DependencyUpdate]: <> (End)

[marker]: <> (End:7745f62d-e15b-4ba3-39b3-08d960f4ca81)
…otnet-runtime build 20231122.29

Microsoft.Internal.Runtime.AspNetCore.Transport , Microsoft.NET.Runtime.MonoAOTCompiler.Task , Microsoft.NET.Runtime.WebAssembly.Sdk , Microsoft.NETCore.App.Ref , Microsoft.NETCore.App.Runtime.AOT.win-x64.Cross.browser-wasm , Microsoft.NETCore.App.Runtime.win-x64 , Microsoft.NETCore.BrowserDebugHost.Transport
 From Version 6.0.26-servicing.23572.23 -> To Version 6.0.26-servicing.23572.29
…ng/internal/dotnet-runtime

This pull request updates the following dependencies

[marker]: <> (Begin:7745f62d-e15b-4ba3-39b3-08d960f4ca81)
## From https://dev.azure.com/dnceng/internal/_git/dotnet-runtime
- **Subscription**: 7745f62d-e15b-4ba3-39b3-08d960f4ca81
- **Build**: 20231122.29
- **Date Produced**: November 23, 2023 9:29:33 AM UTC
- **Commit**: 965a793efc765ddbea3c43e43c13b8e956b61946
- **Branch**: refs/heads/internal/release/6.0

[DependencyUpdate]: <> (Begin)

- **Updates**:
  - **Microsoft.Internal.Runtime.AspNetCore.Transport**: [from 6.0.26-servicing.23572.23 to 6.0.26-servicing.23572.29][1]
  - **Microsoft.NET.Runtime.MonoAOTCompiler.Task**: [from 6.0.26 to 6.0.26][1]
  - **Microsoft.NET.Runtime.WebAssembly.Sdk**: [from 6.0.26 to 6.0.26][1]
  - **Microsoft.NETCore.App.Ref**: [from 6.0.26 to 6.0.26][1]
  - **Microsoft.NETCore.App.Runtime.AOT.win-x64.Cross.browser-wasm**: [from 6.0.26 to 6.0.26][1]
  - **Microsoft.NETCore.App.Runtime.win-x64**: [from 6.0.26 to 6.0.26][1]
  - **Microsoft.NETCore.BrowserDebugHost.Transport**: [from 6.0.26-servicing.23572.23 to 6.0.26-servicing.23572.29][1]

[1]: https://dev.azure.com/dnceng/internal/_git/dotnet-runtime/branches?baseVersion=GC28b24e5d69&targetVersion=GC965a793efc&_a=files

[DependencyUpdate]: <> (End)

[marker]: <> (End:7745f62d-e15b-4ba3-39b3-08d960f4ca81)
…dotnet#52260)

## Issue: Microsoft.AspNetCore.Components.WebView.props is not imported by Maui applications

This issue pertains to the non-importation of Microsoft.AspNetCore.Components.WebView.props by Maui applications. The file has been relocated within the package to ensure its correct pickup and importation during the restore/build process.

Fixes dotnet#42348.

## Description

The inability of Maui applications to rely on JavaScript (JS) initializers, particularly in the case of Fluent UI, is impacted by this issue. The runtime searches for the initializer's definition in a specific location, which is configured in the props file of the package.

## Impact on Customers

The malfunction of JS initializers in Blazor Hybrid has significant implications for both library authors and end users.

Library authors may find their libraries' functionality restricted due to this bug. JS initializers, a feature in Blazor, enable library authors to inject scripts onto the page at the start of the app. These scripts can augment functionality, enhance user interfaces, or facilitate third-party service integration. For instance, a library author might employ a JS initializer to inject a script that integrates with a mapping service, thereby providing real-time location updates within a Blazor app. This functionality would be unavailable in Blazor Hybrid apps due to this bug.

End users may be unable to use certain libraries, or those libraries may not function as anticipated in Blazor Hybrid apps. If a user were to use a Blazor Hybrid app that relies on the aforementioned mapping library, they would not receive the real-time location updates that they would in a regular Blazor app. This could result in an inferior user experience, and in some cases, render the app unusable.

Users and library authors are compelled to manually inject the script onto the page, and some functionality (like configuring Blazor before it starts) is not available in this mode.

## Regression?

- [ ] Yes
- [X] No

## Risk

- [ ] High
- [ ] Medium
- [X] Low

The failure to load a file from a NuGet package impacts the build. The change causes the file to load at build time, enabling the rest of the pipeline to function as expected.

## Verification

- [X] Manual (required)
- [ ] Automated

The changes were made locally on the package cache and ensured the file got imported.

## Packaging changes reviewed?

- [ ] Yes
- [ ] No
- [x] N/A

## When servicing release/2.1

- [ ] Make necessary changes in eng/PatchConfig.props
Merge from public release/6.0 to internal/release/6.0 and resolve conflicts if necessary
Bumps [src/submodules/googletest](https://github.com/google/googletest) from `b10fad3` to `76bb2af`.
- [Release notes](https://github.com/google/googletest/releases)
- [Commits](google/googletest@b10fad3...76bb2af)

---
updated-dependencies:
- dependency-name: src/submodules/googletest
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [src/submodules/spa-templates](https://github.com/dotnet/spa-templates) from `99a804e` to `0e12deb`.
- [Commits](dotnet/spa-templates@99a804e...0e12deb)

---
updated-dependencies:
- dependency-name: src/submodules/spa-templates
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…ng/internal/dotnet-runtime

This pull request updates the following dependencies

[marker]: <> (Begin:7745f62d-e15b-4ba3-39b3-08d960f4ca81)
## From https://dev.azure.com/dnceng/internal/_git/dotnet-runtime
- **Subscription**: 7745f62d-e15b-4ba3-39b3-08d960f4ca81
- **Build**: 20231205.8
- **Date Produced**: December 5, 2023 9:01:32 PM UTC
- **Commit**: dc45e96840243b203b13e61952230e225d2aac52
- **Branch**: refs/heads/internal/release/6.0

[DependencyUpdate]: <> (Begin)

- **Updates**:
  - **Microsoft.Internal.Runtime.AspNetCore.Transport**: [from 6.0.26-servicing.23572.29 to 6.0.26-servicing.23605.8][1]
  - **Microsoft.NET.Runtime.MonoAOTCompiler.Task**: [from 6.0.26 to 6.0.26][1]
  - **Microsoft.NET.Runtime.WebAssembly.Sdk**: [from 6.0.26 to 6.0.26][1]
  - **Microsoft.NETCore.App.Ref**: [from 6.0.26 to 6.0.26][1]
  - **Microsoft.NETCore.App.Runtime.AOT.win-x64.Cross.browser-wasm**: [from 6.0.26 to 6.0.26][1]
  - **Microsoft.NETCore.App.Runtime.win-x64**: [from 6.0.26 to 6.0.26][1]
  - **Microsoft.NETCore.BrowserDebugHost.Transport**: [from 6.0.26-servicing.23572.29 to 6.0.26-servicing.23605.8][1]

[1]: https://dev.azure.com/dnceng/internal/_git/dotnet-runtime/branches?baseVersion=GC965a793efc&targetVersion=GCdc45e96840&_a=files

[DependencyUpdate]: <> (End)

[marker]: <> (End:7745f62d-e15b-4ba3-39b3-08d960f4ca81)
# Conflicts:
#	NuGet.config
#	eng/Version.Details.xml
#	eng/Versions.props
#	global.json
JIT-96177: Update to AspNetCore 6.0.25.
JIT-97707: Update to aspnetcore 6.0.26
refs JIT-97707
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.