Vscode-powershell: Non-preview extension reports "Preview"

[dbaileyut]

System Details

System Details Output

### VSCode version: 1.46.0 a5d1cc28bb5da32ec67e86cc50f84c67cc690321 x64

### VSCode extensions:
[email protected]
[email protected]      
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]        
[email protected]      
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]


### PSES version: 2.2.0.0

### PowerShell version:

Name                           Value
----                           -----
PSVersion                      5.1.19041.1
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.19041.1
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Issue Description

The production release includes "(Preview)" references when it is not preview.

Expected Behaviour

The extension metadata should not not indicate it is Preview

Actual Behaviour

The production release appears to be preview

Via browser:

Attached Logs

Follow the instructions in the troubleshooting docs
about capturing and sending logs.

[SydneyhSmith]

@dbaileyut thanks for opening this, luckily this is purely cosmetic but we will make sure to fix the error in the next release

[ghost]

I also have this issue.

[corbob]

Would it be possible to release another stable version? Or at least re-release 2020.6.0 without the preview tag? I'm still running into people mentioning that they're on the preview version when they're on the stable version (or asking which preview version they should be on).

[JeremyTBradshaw]

I was here today to open an issue for this, searched and found this already opened issue. So will just add that I too notice the issue and it caused me to take extra time figuring out what version I was on when getting support for another issue.

[SydneyhSmith]

Thanks everyone, we will be sure to get this right on our next release (hopefully coming this month)

[andschwa]

This was resolved in #3207