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

[automated] Merge branch 'release/7.0.1xx' => 'release/7.0.3xx' #33067

Conversation

dotnet-maestro-bot
Copy link
Contributor

I detected changes in the release/7.0.1xx branch which have not been merged yet to release/7.0.3xx. I'm a robot and am configured to help you automatically keep release/7.0.3xx up to date, so I've opened this PR.

This PR merges commits made on release/7.0.1xx by the following committers:

  • marcpopMSFT
  • vseanreesermsft
  • v-wuzhai
  • dotnet-maestro[bot]
  • dtivel

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.

merge button instructions

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.

git fetch
git checkout release/7.0.1xx
git pull --ff-only
git checkout release/7.0.3xx
git pull --ff-only
git merge --no-ff release/7.0.1xx

# If there are merge conflicts, resolve them and then run git merge --continue to complete the merge
# Pushing the changes to the PR branch will re-trigger PR validation.
git push https://github.com/dotnet-maestro-bot/sdk HEAD:merge/release/7.0.1xx-to-release/7.0.3xx
or if you are using SSH
git push git@github.com:dotnet-maestro-bot/sdk HEAD:merge/release/7.0.1xx-to-release/7.0.3xx

After PR checks are complete push the branch

git push

Instructions for resolving conflicts

⚠️ If there are merge conflicts, you will need to resolve them manually before merging. You can do this using GitHub or using the command line.

Instructions for updating this pull request

Contributors to this repo have permission update this pull request by pushing to the branch 'merge/release/7.0.1xx-to-release/7.0.3xx'. This can be done to resolve conflicts or make other changes to this pull request before it is merged.

git checkout -b merge/release/7.0.1xx-to-release/7.0.3xx release/7.0.3xx
git pull https://github.com/dotnet-maestro-bot/sdk merge/release/7.0.1xx-to-release/7.0.3xx
(make changes)
git commit -m "Updated PR with my changes"
git push https://github.com/dotnet-maestro-bot/sdk HEAD:merge/release/7.0.1xx-to-release/7.0.3xx
or if you are using SSH
git checkout -b merge/release/7.0.1xx-to-release/7.0.3xx release/7.0.3xx
git pull git@github.com:dotnet-maestro-bot/sdk merge/release/7.0.1xx-to-release/7.0.3xx
(make changes)
git commit -m "Updated PR with my changes"
git push git@github.com:dotnet-maestro-bot/sdk HEAD:merge/release/7.0.1xx-to-release/7.0.3xx

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.

dtivel and others added 15 commits May 16, 2023 15:29
…0518.3

Microsoft.Build , Microsoft.Build.Localization
 From Version 17.4.3 -> To Version 17.4.4
Backport of dotnet#32426

Context: https://aka.ms/maui-support-policy
Context: dotnet/android#8030

For out-of-support .NET 6 MAUI projects, we'd like to emit the warning:

    Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.EolTargetFrameworks.targets(35,5):
    warning NETSDK1202: The workload 'android' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/maui-support-policy for more information about the support policy.

Where each optional workload can opt into this warning via `AutoImport.props`:

    <ItemGroup Condition=" '$(TargetPlatformIdentifier)' == 'android' and $([MSBuild]::VersionEquals($(TargetFrameworkVersion), '6.0')) ">
      <EolWorkload Include="android" Url="https://aka.ms/maui-support-policy" />
    </ItemGroup>

We would add to this MSBuild item group in the `android`, `ios`, `macos`, `maccatalyst`, `tvos` and `maui` workloads. In the future, `wasm-tools` could opt into the warning and leave `%(Url)` blank if desired.

Customers can opt out of the warning in their `.csproj` by either:

    <PropertyGroup>
      <CheckEolWorkloads>false</CheckEolWorkloads>
    </PropertyGroup>
    <ItemGroup>
      <EolWorkload Remove="android" />
    </ItemGroup>

See dotnet/android#8030 for the exact changes we'd make in optional workloads.
…519.1

dotnet-format
 From Version 7.0.357101 -> To Version 7.0.426901
…519.3

dotnet-format
 From Version 7.0.357101 -> To Version 7.0.426903
…519.5

dotnet-format
 From Version 7.0.357101 -> To Version 7.0.426905
…519.10

dotnet-format
 From Version 7.0.357101 -> To Version 7.1.426910
@dotnet-maestro-bot dotnet-maestro-bot force-pushed the merge/release/7.0.1xx-to-release/7.0.3xx branch from 5ffc9c8 to 7f0590e Compare June 7, 2023 06:15
@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Infrastructure untriaged Request triage from a team member labels Jun 7, 2023
@v-wuzhai v-wuzhai force-pushed the merge/release/7.0.1xx-to-release/7.0.3xx branch from ceeea5b to 132c38c Compare June 7, 2023 09:55
@v-wuzhai
Copy link
Member

v-wuzhai commented Jun 7, 2023

@jonathanpeppers would you be able to review these changes please?

@marcpopMSFT
Copy link
Member

@dotnet/sdk-container-builds-maintainers a bunch of containers tests failed with the same error: Get "http://localhost:5010/v2/": read tcp 127.0.0.1:40054->127.0.0.1:5010: read: connection reset by peer Rerunning as I assume that's stability and I added a comment to #28442

@JL03-Yue JL03-Yue merged commit 600db18 into dotnet:release/7.0.3xx Jun 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Infrastructure untriaged Request triage from a team member
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants