Releases: PowerShell/PSScriptAnalyzer
Releases · PowerShell/PSScriptAnalyzer
1.25.0
Sorry, something went wrong.
No results found
What's Changed
New Contributors
Full Changelog: 1.24.0...1.25.0
1.24.0
Sorry, something went wrong.
No results found
What's Changed
Breaking Changes
Minimum required PowerShell version raised from 3 to 5.1
New Features
- Add new options (enabled by default) to formatting rule UseCorrectCasing to also correct operators, keywords and commands - Add UseConsistentCasing by Joel Bennett (@Jaykul) in #1704
Enhancements
Bug Fixes
Process Changes
New Contributors
Full Changelog: 1.23.0...1.24.0
1.23.0
Sorry, something went wrong.
No results found
What's Changed
New Contributors
Full Changelog: 1.22.0...1.23.0
PSScriptAnalyzer v1.22.0
Sorry, something went wrong.
No results found
Minimum required version when using PowerShell 7 is now 7.2.11.
New Rule
Enhancements
Fixes
Build & Test, Documentation and Maintenance
New Contributors
Full Changelog: 1.21.0...1.22.0
PSScriptAnalyzer v1.21.0
Sorry, something went wrong.
No results found
1.21.0 - 2022-09-14
New Rule
Enhancements
Fixes
Build, Documentation and Maintenance
PSScriptAnalyzer v1.20.0
Sorry, something went wrong.
No results found
1.20.0 - 2021-08-20
Fixes
New Rule
Miscellaneous
Documentation
Testing
Development/Build Improvements
PSScriptAnalyzer v1.19.1
Sorry, something went wrong.
No results found
Fixes
New Rule
Miscellaneous
Documentation
Testing
Development improvements
PSScriptAnalyzer v1.19.0
Sorry, something went wrong.
No results found
New Rules
Rule Enhancements
Compatibility Rules
Formatter
- UseCorrectCasing
- UseConsistentIndentation
- When non-default options are used, cater for the case of a comment between pipe and newline (#1463)
- Add PipelineIndentationStyle.None option for scenarios where indentation is custom, inconsistent or the user does not like any of the 3 pipeline indentation styles (#1399) (by Christoph Bergmeister (@bergmeister))
- Fix complex case when PipelineIndentation is not set to default (NoIndentation) (#1359) (by Christoph Bergmeister (@bergmeister))
- UseConsistentWhitespace
Performance
The Formatter can now be multiple times faster depending on the use case and especially scaling problems were addressed that showed when analyzing large scripts with thousands of lines (a 3000 line test script was used in the below performance figures). Optimisations were to
- Eliminate initialization overhead, which can lead to a reduced time of up to 50%
- Optimize operations in rules to make them scale better, another improvement of around 50%
- The formatter used to re-parse the script in between every rule run but this is skipped now if the previous rule did not emit a DiagnosticRecord as it means the script text hasn't changed and doesn't need updating. Therefore formatting will be faster on scripts that need no to little changes.
A small improvement was made to a script analysis rule as well but the gain is offset by the addition of the new rules in this release.
The PRs for those improvements are:
Fixes
Build/Tests/Maintenance
Documentation
PSScriptAnalyzer v1.18.3
Sorry, something went wrong.
No results found
This release adds one more important fix, which prevents a leak of runspaces when repeatedly invoking the PSScriptAnalyzer cmdlets. Furthermore it ups the minimum version of PowerShell Core to 6.2.0 due to 6.1 reaching its end of life this month.
PSScriptAnalyzer v1.18.2
Sorry, something went wrong.
No results found
This release mainly brings fixes and enhancements that are especially useful when being consumed by PowerShellEditorServices.
The benefit to the user will be some enhancements and fixes in the formatter, especially around multiline commands. In addition to that, error messages emitted when using invalid syntax in the setting file are now much more meaningful and actionable.
Fixes
-
Compatibility Analysis
-
Formatter
-
Engine
Enhancements
Documentation
Build