PowerShell / PowerShell/PSScriptAnalyzer
Consider publishing pre-releases
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 414
- Avg merge
- 13h 1m
- Merged PRs (30d)
- 2
Description
Since the PSGallery supports pre-releases now, this would be a good opportunity to test the waters before the next version goes out into the wild. We had the upgrade to the new SDK, which was a big change and hopefully it has not broken anything and also new parameters like e.g. -Fix and EnableExit that people could play with and give feedback.
Given that PSSA gets integrated into the PowerShellEditorServices and via that lands in the PowerShell extension of VSCode (which has 2 million installs) we should be aware that new problem of PSSA could have a bigger impact. I had a chat with the guys here and VSCode does not have native support for pre-release but they could offer a pre-release VSIX package at least, which could add to the userbase of pre-release testers.
Let me know your thoughts and what kind of (pre)release frequency is preferred?
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.
Research direction
Start by reviewing the proposed PSGallery pre-release workflow and its relationship to PowerShellEditorServices and the PowerShell VSCode extension. Define the supported pre-release and release frequency, along with how feedback from pre-release testers would be collected and acted on.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, vscode
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100