Repository navigation
Lack of compatibility profiles for current PowerShell Core versions, Windows 11, Windows PowerShell on Windows 11. #2152
Description
Summary of the new feature
Add compatibility profiles for current PowerShell Core versions, Windows 11, Windows PowerShell on Windows 11, potentially other supported OS/PowerShell combinations as outlined by https://learn.microsoft.com/en-us/powershell/scripting/install/powershell-support-lifecycle
As a user, I would like to be able to leverage the PSUseCompatibleCommands check against profiles reflecting the current state of the OS and PowerShell, rather than only dated profiles reflecting unsupported OS and PowerShell versions. I am not proposing removal of any old profiles, just creation of new ones and relocation of unsupported ones to the optional directory.
Proposed technical implementation details (optional)
It would be nice if the process to generate these was added to the CI process, so that as Windows and PS Core versions move forward, new profiles are automatically generated.
What is the latest version of PSScriptAnalyzer at the point of writing
1.24.0
Activity
ajn142 commentedon Jan 24, 2026
If the process outlined in #1657 is still accurate to generate profiles, I can potentially generate ones reflecting my current OSs and PowerShell versions and submit a PR, but I think implementing a CI process to build new profiles and retire old ones as optional would be a better overall fit. It's also unclear to me whether the process will include or bypass any modules I've written or installed beyond those available in base PowerShell, as I'd hate to contaminate the profiles with commands that aren't actually present on all installs.
bergmeister commentedon Mar 31, 2026
Yes, you can create your own profiles, we'd be happy to accept a PR for it. Preferably from an image that is used in GitHub Actions or Azure DevOps.