Closed bergmeister closed 5 years ago
Does this have any advantages or disadvantages? E.g. could it break compatibility with older PowerShell Core versions?
This just so that the built .Net binaries were built using the latest patched version of msbuild as there are usually security related fixed in SDK updates, in the meantime the latest LTS version is already 2.1.801 (too new for Travis at the moment, so I went back to 2.1.700
)
https://dotnet.microsoft.com/download/dotnet-core/2.1
Since we use .Net Standard now, we could even use the 2.2 SDK now, which might have faster build times, 2.1 is fine as well though and has LTS (long term support). This does not affect PS at all, what matters is the runtime target in the csproj (which is now netstandard2.0
, on which any version of PSCore can run, even 7.0)
I'd be down for 2.2, wanna do that?
yes, we can definitely try that. Let's see if travis supports it. Technically we could already go for 3.0-preview because, which is already supported for production but will be released anyway in a month at .net conf
Ok, it seems this travis environment does not support 2.2 well. I suggest to update trusty
to xenial
(i.e. Ubuntu 14 to 16). Mainstream support for Ubuntu 14 has already ended and PowerShell is not supporting it any more. I'd say that is another PR though...
I already switched to xenial in #38
Pushed to master
Ok, thanks, it worked now :-)
:tada: This PR is included in version 0.11.1 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
Codecov Report
Continue to review full report at Codecov.