Merging internal commits for release/7.0 #49338
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…iled if updating AccessFailedCount fails
…t-efcore dnceng/internal/dotnet-runtime
Merge from public release/7.0 to internal/release/7.0 and resolve conflicts if necessary
…ng/internal/dotnet-runtime This pull request updates the following dependencies [marker]: <> (Begin:2802be6f-a6f7-477e-8165-08da7ef6284d) ## From https://dev.azure.com/dnceng/internal/_git/dotnet-runtime - **Subscription**: 2802be6f-a6f7-477e-8165-08da7ef6284d - **Build**: 20230620.18 - **Date Produced**: June 20, 2023 11:21:08 PM UTC - **Commit**: 8e9a17b2216f51a5788f8b1c467a4cf3b769e7d7 - **Branch**: refs/heads/internal/release/7.0 [DependencyUpdate]: <> (Begin) - **Updates**: - **Microsoft.Internal.Runtime.AspNetCore.Transport**: [from 7.0.9-servicing.23320.4 to 7.0.9-servicing.23320.18][1] - **Microsoft.NET.Runtime.MonoAOTCompiler.Task**: [from 7.0.9 to 7.0.9][1] - **Microsoft.NET.Runtime.WebAssembly.Sdk**: [from 7.0.9 to 7.0.9][1] - **Microsoft.NETCore.App.Ref**: [from 7.0.9 to 7.0.9][1] - **Microsoft.NETCore.App.Runtime.AOT.win-x64.Cross.browser-wasm**: [from 7.0.9 to 7.0.9][1] - **Microsoft.NETCore.App.Runtime.win-x64**: [from 7.0.9 to 7.0.9][1] - **Microsoft.NETCore.BrowserDebugHost.Transport**: [from 7.0.9-servicing.23320.4 to 7.0.9-servicing.23320.18][1] - **Microsoft.NETCore.Platforms**: [from 7.0.4 to 7.0.4][1] [1]: https://dev.azure.com/dnceng/internal/_git/dotnet-runtime/branches?baseVersion=GCde4755132e&targetVersion=GC8e9a17b221&_a=files [DependencyUpdate]: <> (End) [marker]: <> (End:2802be6f-a6f7-477e-8165-08da7ef6284d)
# {PR title}
Summary of the changes (Less than 80 chars)
## Description
{Detail}
Fixes #{bug number} (in this specific format)
## Customer Impact
{Justification}
## Regression?
- [ ] Yes
- [ ] No
[If yes, specify the version the behavior has regressed from]
## Risk
- [ ] High
- [ ] Medium
- [ ] Low
[Justify the selection above]
## Verification
- [ ] Manual (required)
- [ ] Automated
## Packaging changes reviewed?
- [ ] Yes
- [ ] No
- [ ] N/A
----
## When servicing release/2.1
- [ ] Make necessary changes in eng/PatchConfig.props
Fix shas for July
…-merge-7.0-2023-07-11-1025
|
Hi @vseanreesermsft. If this is not a tell-mode PR, please make sure to follow the instructions laid out in the servicing process document. |
ghost
added
the
area-infrastructure
wtgodbe
approved these changes
Jul 11, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.