Skip to content

[automated] Merge branch 'release/2.1' => 'release/3.1' #18347

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

dotnet-maestro-bot
Copy link
Contributor

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

This PR merges commits made on release/2.1 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.

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/2.1
git pull --ff-only
git checkout release/3.1
git pull --ff-only
git merge --no-ff release/2.1

# 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/AspNetCore HEAD:merge/release/2.1-to-release/3.1
or if you are using SSH
git push [email protected]:dotnet-maestro-bot/AspNetCore HEAD:merge/release/2.1-to-release/3.1

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/2.1-to-release/3.1'. This can be done to resolve conflicts or make other changes to this pull request before it is merged.

git checkout -b merge/release/2.1-to-release/3.1 release/3.1
git pull https://github.com/dotnet-maestro-bot/AspNetCore merge/release/2.1-to-release/3.1
(make changes)
git commit -m "Updated PR with my changes"
git push https://github.com/dotnet-maestro-bot/AspNetCore HEAD:merge/release/2.1-to-release/3.1
or if you are using SSH
git checkout -b merge/release/2.1-to-release/3.1 release/3.1
git pull [email protected]:dotnet-maestro-bot/AspNetCore merge/release/2.1-to-release/3.1
(make changes)
git commit -m "Updated PR with my changes"
git push [email protected]:dotnet-maestro-bot/AspNetCore HEAD:merge/release/2.1-to-release/3.1

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.

BrennanConroy and others added 21 commits November 22, 2019 23:28
Fixed a merge conflict in the code mirror from github into 'internal/release/3.1'
…ositories

This pull request updates the following dependencies

[marker]: <> (Begin:48752c90-f78c-49ee-575f-08d76e1d56cb)
## From https://github.com/aspnet/EntityFrameworkCore
- **Build**: 20191210.7
- **Date Produced**: 12/10/2019 8:25 PM
- **Commit**: 813358a5fb4e1f35e5d82463d2bad6616ca6f594
- **Branch**: refs/heads/internal/release/3.1
- **Updates**:
  - **Microsoft.EntityFrameworkCore.Tools** -> 3.1.1-servicing.19610.7
  - **Microsoft.EntityFrameworkCore.SqlServer** -> 3.1.1-servicing.19610.7
  - **dotnet-ef** -> 3.1.1-servicing.19610.7
  - **Microsoft.EntityFrameworkCore** -> 3.1.1-servicing.19610.7
  - **Microsoft.EntityFrameworkCore.InMemory** -> 3.1.1-servicing.19610.7
  - **Microsoft.EntityFrameworkCore.Relational** -> 3.1.1-servicing.19610.7
  - **Microsoft.EntityFrameworkCore.Sqlite** -> 3.1.1-servicing.19610.7

[marker]: <> (End:48752c90-f78c-49ee-575f-08d76e1d56cb)
…ositories

This pull request updates the following dependencies

[marker]: <> (Begin:facfaf30-1c25-4166-575d-08d76e1d56cb)
## From https://dev.azure.com/dnceng/internal/_git/aspnet-AspNetCore-Tooling
- **Build**: 20191214.11
- **Date Produced**: 12/15/2019 3:03 AM
- **Commit**: 07f16c89db55ab6f9f773cc3db6eb5a52908065e
- **Branch**: refs/heads/internal/release/3.1
- **Updates**:
  - **Microsoft.AspNetCore.Mvc.Razor.Extensions** -> 3.1.1
  - **Microsoft.AspNetCore.Razor.Language** -> 3.1.1
  - **Microsoft.CodeAnalysis.Razor** -> 3.1.1
  - **Microsoft.NET.Sdk.Razor** -> 3.1.1

[marker]: <> (End:facfaf30-1c25-4166-575d-08d76e1d56cb)
@ghost ghost added area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework Type: Merge Forward ⏩ labels Jan 15, 2020
@BrennanConroy
Copy link
Member

Not 3.0? What's with the bot @dotnet/aspnet-build

@dougbu
Copy link
Contributor

dougbu commented Jan 15, 2020

@BrennanConroy the bar is higher for this branch. We are only merging into 'release/3.0' manually i.e. cherry-picks to avoid bringing in unapproved changes.

@dotnet-maestro-bot
Copy link
Contributor Author

This pull request has been updated.

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

1 similar comment
@dotnet-maestro-bot
Copy link
Contributor Author

This pull request has been updated.

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

@analogrelay
Copy link
Contributor

@Tratcher this includes merges from the 2.1 same-site fix. I presume they aren't needed in 3.1 and can be reverted in the merge PR.

@analogrelay
Copy link
Contributor

analogrelay commented Jan 15, 2020

@BrennanConroy SignalR changes are likely the January fixes flowing up now that they've been merged to public? Also, the 2.1 test fix PR.

@BrennanConroy
Copy link
Member

Yep, I'll work with Justin to update it after lunch

</PropertyGroup>
<PropertyGroup Condition=" '$(VersionPrefix)' == '2.1.16' ">
<PackagesInPatch>
Microsoft.AspNetCore.Authentication.Cookies;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These patches aren't needed in 3.1

Suggested change
Microsoft.AspNetCore.Authentication.Cookies;

<PropertyGroup Condition=" '$(VersionPrefix)' == '2.1.16' ">
<PackagesInPatch>
Microsoft.AspNetCore.Authentication.Cookies;
Microsoft.AspNetCore.Mvc.Core;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Microsoft.AspNetCore.Mvc.Core;

@@ -169,6 +169,7 @@ public void AppendResponseCookie(HttpContext context, string key, string value,
HttpOnly = options.HttpOnly,
Path = options.Path,
Secure = options.Secure,
MaxAge = options.MaxAge,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure why changes in this file are showing up, 3.1 already has these.

@@ -21,6 +21,29 @@ public void AppendLargeCookie_Appended()
Assert.Equal("TestCookie=" + testString + "; path=/; samesite=lax", values[0]);
}

[Fact]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

3.1 already has the changes for this file too.

@@ -190,7 +190,7 @@ public async Task RemoteSignoutRequestTriggersSignout()
response.EnsureSuccessStatusCode();

var cookie = response.Headers.GetValues(HeaderNames.SetCookie).Single();
Assert.Equal(".AspNetCore.Cookies=; expires=Thu, 01 Jan 1970 00:00:00 GMT; path=/; samesite=lax", cookie);
Assert.Equal(".AspNetCore.Cookies=; expires=Thu, 01 Jan 1970 00:00:00 GMT; path=/; samesite=lax; httponly", cookie);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ignore, already in 3.1

@@ -44,8 +44,16 @@ Later on, this will be checked using this condition:
Microsoft.AspNetCore.CookiePolicy;
</PackagesInPatch>
</PropertyGroup>
<PropertyGroup Condition=" '$(VersionPrefix)' == '2.1.15' ">
<PropertyGroup Condition=" '$(VersionPrefix)' == '2.1.16' ">
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<PropertyGroup Condition=" '$(VersionPrefix)' == '2.1.16' ">
<PropertyGroup Condition=" '$(VersionPrefix)' == '2.1.15' ">

"TestCookieC4=; expires=Thu, 01 Jan 1970 00:00:00 GMT; domain=foo.com; path=/; samesite=lax",
"TestCookieC5=; expires=Thu, 01 Jan 1970 00:00:00 GMT; domain=foo.com; path=/; samesite=lax",
"TestCookieC6=; expires=Thu, 01 Jan 1970 00:00:00 GMT; domain=foo.com; path=/; samesite=lax",
"TestCookieC7=; expires=Thu, 01 Jan 1970 00:00:00 GMT; domain=foo.com; path=/; samesite=lax",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the 2.2 branch, not the 3.1 branch.

"TestCookie=; expires=Thu, 01 Jan 1970 00:00:00 GMT; domain=foo.com; path=/; samesite=lax",

@BrennanConroy
Copy link
Member

@dotnet/aspnet-build @Tratcher @jkotalik Please take a look ASAP and see if the changes make sense

@@ -0,0 +1 @@

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove these two files?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes please

}
_writeLock.Release();

// Acquire lock to make sure all writes are completed
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fix duped code

@@ -32,6 +32,32 @@ public void Dispose()

var results = _sink.GetLogs().Where(w => w.Write.LogLevel >= LogLevel.Error).ToList();

#if NETCOREAPP2_1 || NETCOREAPP2_2 || NET461
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove

@@ -77,6 +77,12 @@ MSBuild verbosity: q[uiet], m[inimal], n[ormal], d[etailed], and diag[nostic]
.PARAMETER MSBuildArguments
Additional MSBuild arguments to be passed through.

.PARAMETER DotNetRuntimeSourceFeed
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are there changes in the build scripts?

@jkotalik
Copy link
Contributor

Something seems up with the merge. I see 3.1 commits in the list of commits when it should just be 2.1 commits I believe.

Copy link
Member

@Tratcher Tratcher left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For /Security

@jkotalik jkotalik mentioned this pull request Jan 16, 2020
@dotnet-maestro-bot
Copy link
Contributor Author

❌ Uh oh, this pull request could not be updated automatically. New commits were pushed to release/2.1, but I could not automatically push those to merge/release/2.1-to-release/3.1 to update this PR.
You may need to fix this problem by merging branches with this PR. Contact .NET Core Engineering if you are not sure what to do about this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework Type: Merge Forward ⏩
Projects
None yet
Development

Successfully merging this pull request may close these issues.