Powershell5 - Literal Versioning

PowerShell Universal Universal Automation
1

Hello,

I have some scripts that require Pwsh5 (long story), but noticed today that they dropdown to select version is the literal installed versions. This created an issue where over the weekend servers patched, Powershell5 got a small patch, and my scripts broke as they were set to use a version that was no longer installed.

Is there any way to variable-ize the version, or would it be a feature request to add “fuzzy” versioning?

Thanks!

Product: PowerShell Universal
Version: 1.4.6
2

The environment name is just what we look up when PSU is first run. It doesn’t actually pin it to a specific PS version. What PSU is really relying on is the path that is defined. With an upgrade of Windows, I would not expect the jobs to break so I’d be curious what issue you were seeing.