Dongbo Wang

It's helpful to ignore the whitespace changes during the review: https://github.com/PowerShell/PowerShell/pull/19525/files?w=1

Still waiting on the committee to make a conclusion.

@JamesWTruher A few questions: > but just typing `Start-ThreadJob` will auto-load the new `Microsoft.PowerShell.ThreadJob` module 1. How would we guarantee `Microsoft.PowerShell.ThreadJob` will be the one loaded when just typing `Start-ThreadJob`?...

The proxy module shouldn't be developed in this PR, as the code should be in a different repo. If this PR is blocked on that, then I will close this...

But `ThreadJob` is a published module in PowerShell Gallery (v2.0.3 now). If we are going to have a proxy module for it, we'd better release it to PowerShell Gallery too,...

Opened https://github.com/PowerShell/ThreadJob/issues/30 to track the proxy module work. I will close this PR for now.

@SteveL-MSFT Did you take a look at https://github.com/PowerShell/PowerShell/pull/19780 and see if it tries to fix the same?

@Francisco-Gamino I cannot reproduce the issue within `pwsh` by following the repro steps. Theoretically, the parsing of the `psm1` file doesn't require a custom type to be resolved unless the...

Engine Working Group reviewed this today. You can set the `POWERSHELL_UPDATECHECK` environment variable to `LTS`, then it will only notify of updates to long-term-servicing (LTS) GA releases. See https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_update_notifications?view=powershell-7.3

@kilasuit The "PowerShell-CI-install-ps" job failed, which is likely caused by the changes in this PR. Please take a look.