Lack of compatibility profiles for current PowerShell Core versions, Windows 11, Windows PowerShell on Windows 11.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- powershell
- Domain
- tooling
Research direction
Start by reviewing the existing PSUseCompatibleCommands compatibility profiles and the PowerShell support lifecycle linked in the issue. Determine which current PowerShell Core, Windows 11, and Windows PowerShell combinations need profiles, and how unsupported profiles are organized in the optional directory. Done means current profiles are available without removing older ones, with CI generation investigated as part of the implementation.
Written by the indexing model from the issue text.
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
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 415
- Avg merge
- 13h 1m
- Merged PRs (30d)
- 2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PowerShell/PSScriptAnalyzer
-
Up-for-Grabs
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
PowerShell/PSScriptAnalyzer#2213 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
PowerShell/PSScriptAnalyzer#2217 · 1 comment ·
-
PSUseConsistentIndentation double-indents attribute bodies that open a scriptblock (`[Attr({ … })]`) Open
Difficulty 3/5 1-2 days Newbie friendliness 70/100
PowerShell/PSScriptAnalyzer#2216 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
PowerShell/PSScriptAnalyzer#2211 ·
-
`PSPlaceOpenBrace` and `PSPlaceCloseBrace` leave trailing whitespace when expanding one-line blocks Open
Difficulty 3/5 1-2 days Newbie friendliness 70/100
PowerShell/PSScriptAnalyzer#2210 ·
All issues in PowerShell/PSScriptAnalyzer
Similar issues
-
:watch: Not Triaged dotnet-fsharp/svc
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Client customer-reported needs-team-attention question Service Attention WebPubSub
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Azure/azure-sdk-for-net#63292 · 3 comments · 1 reaction ·
-
Issue-Enhancement Needs-Triage
Difficulty 1/5 Under an hour Newbie friendliness 86/100
PowerShell/PowerShell#28061 · 2 reactions ·
-
dependencies needs-team-triage server-Azure.Mcp
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
aspnet-core/svc aspnetcore-signalr/subsvc doc-enhancement Pri2 SignalR
Difficulty 1/5 Under an hour Newbie friendliness 88/100
dotnet/AspNetCore.Docs#37729 ·