PowerShell SDK 7.6.0 - wrong $PSVersionTable.PSVersion

[nightroman]

Prerequisites

• Write a descriptive title.
• Make sure you are able to repro it on the latest released version
• Search the existing issues.
• Refer to the FAQ.
• Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce

(1) Create and build an application hosting PowerShell SDK 7.6.0 (this scenario does not show the bug)
(1) Create an application which loads an assembly hosting PowerShell SDK 7.6.0 (addon scenario)

(2) Invoke some method in this assembly witch gets and returns $PSVersionTable

NB My existing app and addon are too complex to present here. I will try to build a simple demo app.
But I keep the issue, just in case the team has some ideas why this happens.

Expected behavior

`PSVersion` is 7.6.0

Actual behavior

`PSVersion` is 7.5.4

Environment data

Note: it shows the wrong version, it should show 7.6.0


Name                           Value
----                           -----
PSVersion                      7.5.4
PSEdition                      Core
GitCommitId                    7.5.4
OS                             Microsoft Windows 10.0.26200
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Visuals

No response

[nightroman]

@doterik Are you using the installed pwsh or an app built with PowerShell SDK as described in steps to repro?

[doterik]

@nightroman WinGet showed me an update that I installed, didn't realize you were talking about the SDK...

[kilasuit]

@nightroman

I can't replicate this with a console app hosting the SDK

With this program.cs

using System.Management.Automation;
using System.Management.Automation.Language;

using (PowerShell ps = PowerShell.Create())
{
    ps.AddScript("$PSVersionTable | out-String");
    var results = ps.Invoke();

    foreach (var result in results)
    {
        Console.WriteLine(result);
    }
}

& this consolepwshsdk.csproj file

<Project Sdk="Microsoft.NET.Sdk">

  <ItemGroup>
    <PackageReference Include="Microsoft.PowerShell.SDK" Version="7.6.0" />
  </ItemGroup>
  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net10.0</TargetFramework>
    <ImplicitUsings>enable</ImplicitUsings>
    <Nullable>enable</Nullable>
  </PropertyGroup>

</Project>

[nightroman]

@kilasuit I see, thank you for doing my homework, I should have checked this myself. I just hoped that any app with SDK shows the bug.

The thing is my actual scenario is more complex. The app is native, it hosts dotnet 10 runner and then loads PowerShell as one of the addons. Apparently, I need to build a minimal repro case with similar setup.

I'll keep the issue open for a while, just in case if PowerShell team has ideas why this happens. And I'll change the description.

[nightroman]

This is creasy, I saw this bug and double checked it. Not sure what I have done (a few changes) but the issue is no more.
Phew, sorry All for the false alarm, closing.