-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[automated] Merge branch 'release/6.0-rc2' => 'release/6.0' #36629
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/6.0-rc2' => 'release/6.0' #36629
Conversation
This reverts commit f4cc3c0. Co-authored-by: Sébastien Ros <[email protected]>
ghost
left a comment
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.
…tnet#36590) * Add support for BindAsync without ParameterInfo * Update src/Shared/ParameterBindingMethodCache.cs Co-authored-by: David Fowler <[email protected]> * Apply suggestions from code review * named tuple Co-authored-by: Brennan <[email protected]> Co-authored-by: David Fowler <[email protected]>
…rse (dotnet#36588) * Fixup OpenAPI displayed param type when using TryParse * nullable Co-authored-by: Brennan <[email protected]>
[release/6.0-rc2] Update dependencies from dotnet/runtime - Update CreateFrameworkListFile to account for new analyzer path format introduced with dotnet/sdk#20355
|
I'm confused. Where are the package version changes coming from❔ Don't we want RTM packages from dotnet/runtime in this branch (if they're available -- @Anipik ❔). |
From the RC2 branch.
I don't think there has been an RTM dependency update to the 6.0 branch yet so isn't this expected |
I think there was one but hopefully nothing introducing RC1 / RC2 incompatibilities. We need to get a clean build to be sure but keep hitting infrastructure issues. Second try is almost ready for another attempt In case someone else is up to hit the buttons in AzDO, I'm enabling an auto-merge here. |
I detected changes in the release/6.0-rc2 branch which have not been merged yet to release/6.0. I'm a robot and am configured to help you automatically keep release/6.0 up to date, so I've opened this PR.
This PR merges commits made on release/6.0-rc2 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/6.0-rc2-to-release/6.0'. 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.