Remove the use of Windows PowerShell ETW provider id and update `PSDiagnostics` module to work for PowerShell 7 by daxian-dbw · Pull Request #25590

Remove the use of Windows PowerShell ETW provider id and update `PSDiagnostics` module to work for PowerShell 7 by daxian-dbw · Pull Request #25590 · PowerShell/PowerShell

I'm not really too familiar with the ETW side and the PSDiagnostics module but wouldn't this be a breaking change? Right now the PSDiagnostics module is importable in PS 7 and manages the WinPS provider. While I understand trying to keep the providers aligned with the PowerShell version used there could potentially be people using PS 7 to manage the WinPS provider in this module.

The change to PSDiagnostics is a breaking change. It breaks the scenario where a user intentionally uses PowerShell 7+ to enable/disable Windows PowerShell ETW tracing. But is that a real-world scenario?

This module is shipped with PowerShell 7, so intuitively, running Enable-PSTrace from this module should enable the PowerShellCore provider instead of the Windows PowerShell ETW provider.