Remove the reference to 3.1.102 in the .Net Core SDK installation scripts

[SeanFarrow]

Now that .Net Core sdk 3.1.201 has been released, do we need to concern ourselves with
this
issue?
If not, I'm happy to update the scripts to remove all checks for 3.1.102.
Thanks,
Sean.

[dsame]

The changes have been merged and are in the deploy process

[miketimofeev]

@SeanFarrow we've removed all checks and 3.1.102 is presented on all the images. I'm going to close the issue, but feel free to contact us if you have any concerns.
Thank you!

[SeanFarrow]

Hi, Thanks for doing this. Does this mean it will use the latest SDK at the time the image is updated? My concern is the fact that the .Net core 3 SDK is updated and these images will not receive updates in a timely fashion. From: Mikhail Timofeev <[email protected]> Sent: 11 June 2020 07:19 To: actions/virtual-environments <[email protected]> Cc: Sean Farrow <[email protected]>; Mention <[email protected]> Subject: Re: [actions/virtual-environments] Remove the reference to 3.1.102 in the .Net Core SDK installation scripts (#673) Closed #673<#673>. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#673 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AALDK7ULXFDDXCPOEUE6LWDRWBZPBANCNFSM4L4VQ5QA>.

[AlenaSviridenko]

Hi @SeanFarrow,
we are using the latest stable released .Net Core SDK from GitHub releases as the default one, so for .Net Core 3 SDK the latest one is the 3.1.301. It will be updated automatically to the next one with new release in .Net Core 3 SDK