-
-
Notifications
You must be signed in to change notification settings - Fork 473
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
Drop support for PowerShell v3 and v4? #2324
Comments
Once this is done, will versions of Pester supporting Powershell v3 or v4 continue to be maintained in the event of a blocking bug? |
Note: This issue is not a accepted change at this point. Just an issue for discussing it and tracking pros/cons. Might convert it to a discussion topic 🙂
Like v4 now it'd likely get critical fixes and security patches, but at that point v5 should be very stable. All OSs compatible with PSv3/v4 won't get any updates so there's a low risk of anything breaking. |
Resolved in #2432. Keeping open until released and we start working on the previously blocked issues. |
FYI Windows Server 2012 is supported under the Microsoft Extended Security Updates program until 2026-10-13: https://learn.microsoft.com/en-us/lifecycle/products/windows-server-2012 |
ESU is a paid service that Microsoft provides, this module is free. We can do paid support probably, but so far nobody asked us for that. |
I think it's not unreasonable to drop support in the next major version of Pester, just pointing out PSv3/PSv4 are still supported by Microsoft. |
@nohwnd Just noticed the Pester supported versions information in SECURITY.md has not been updated for many years. |
Completed by #2432 released in 6.0.0-alpha1 |
Windows Server 2012/2012R2 will be end of life October 10, 2023. From that point on only PowerShell v5.1 and later is supported by Microsoft and we should consider dropping support for PSv3 and PSv4.
Using this issue to track features and changes being blocked by PSv3 and PSv4:
::new()
,.Where({})
,.ForEach({})
and other language features to replace calls to slower*-Object
cmdlets etc.net461
due to Windows Server 2016 OOB version)? See PowerShellStandardWrite-Host
writes to information stream (NUnit XML does not contain output logging for the cmdlets #301)The text was updated successfully, but these errors were encountered: