Skip to content

Bump .NET to version 5.0.100-rtm.20526.5 #13920

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

Merged

Conversation

adityapatwardhan
Copy link
Member

@adityapatwardhan adityapatwardhan commented Oct 29, 2020

PR Summary

Update to the latest version of .NET 5

PR Context

PR Checklist

@ghost ghost assigned TravisEz13 Oct 29, 2020
@adityapatwardhan adityapatwardhan changed the title Bump .NET to version 5.0.100-rtm.20526.5 WIP: Bump .NET to version 5.0.100-rtm.20526.5 Oct 29, 2020
@adityapatwardhan adityapatwardhan changed the title WIP: Bump .NET to version 5.0.100-rtm.20526.5 Bump .NET to version 5.0.100-rtm.20526.5 Nov 2, 2020
@adityapatwardhan adityapatwardhan merged commit e99f055 into PowerShell:master Nov 3, 2020
@adityapatwardhan adityapatwardhan deleted the UpdateNET5RTM_2 branch November 3, 2020 00:51
@adityapatwardhan adityapatwardhan added the CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log label Nov 4, 2020
@adityapatwardhan adityapatwardhan added this to the 7.1.0 milestone Nov 4, 2020
daxian-dbw pushed a commit to daxian-dbw/PowerShell that referenced this pull request Nov 10, 2020
@ghost
Copy link

ghost commented Nov 11, 2020

🎉v7.1.0 has been released which incorporates this pull request.:tada:

Handy links:

@ghost
Copy link

ghost commented Nov 17, 2020

🎉v7.2.0-preview.1 has been released which incorporates this pull request.:tada:

Handy links:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BackPort-7.1.x-Done Backport to 7.1.x completed CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants