Releases: PowerShell/PSScriptAnalyzer
PSScriptAnalyzer v1.11.0
Please see the CHANGELOG for information about the changes in this release.
You can download this version from PowerShellGallery.
PSScriptAnalyzer v1.10.0
This release adds code formatting rules and other bug fixes. Please the CHANGELOG for more details.
You can download this version from PowerShellGallery
PSScriptAnalyzer v1.9.0
This release adds two new rules: AvoidGlobalAliases and AvoidGlobalFunctions and numerous bug fixes. Please see the CHANGELOG for more details.
A big Thank You! to @dcrreynolds for contributing the two new rules.
You can download this version from PowerShellGallery.
PSScriptAnalyzer v1.8.1
This release fixes bugs in PSUsePSCredentialType
and PSUseShouldProcessForStateChangingFunctions
rules. It also adds a digitally signed catalog file so to work with PowerShellGet v1.1.0.0. For more information please see the CHANGELOG.
You can download the latest version from PowerShell Gallery.
PSScriptAnalyzer v1.8.0
For this release we have added two new rules, (UseCompatibleCmdlets and UseLiteralInitializerForHashtable), features like auto discovery of settings file and rule configuration through settings file, and other enhancements and bug fixes. Please checkout CHANGELOG for more details. For a more granular changelog please see this.
You can download the latest version from PowerShell Gallery
PSScriptAnalyzer v1.7.0
This release rolls out support on PowerShell Core edition and other bug fixes. Please see changelog.md for the changes.
You can download the latest version from PowerShell Gallery
PSScriptAnalyzer v1.6.0
This release contains numerous rules and engine bug fixes along with the following two major feature additions.
This release adds a switch named SaveDSCDepenency
to Invoke-ScriptAnalyzer
. As the name suggests, when this switch is provided, we allow PSSA to download DSC resources from PSGallery whenever it encounters ModuleNotFoundDuringParse
error in the context of Import-DSCResource
keyword. For more information about this feature please have a look at #520 and #524 .
A new property, SuggestedCorrections
is added to DiagnosticRecord
. This feature facilitates quick-fix scenarios in editors that use PSSA to provide users with diagnostic information about the PowerShell scripts that are being edited. Whenever a rule violation occurs, PSSA provides a valid SuggestedCorrections property in the emitted DiagnosticRecord objects. This provides information about the violation extent and the correction that can rectify the violation. For more information about this feature please have a look at #502, #508 and #516.
You can grab this version from PowerShellGallery at https://www.powershellgallery.com/packages/PSScriptAnalyzer/1.6.0
Detailed change log can be found at https://github.com/PowerShell/PSScriptAnalyzer/blob/master/CHANGELOG.MD
PSScriptAnalyzer v1.5.0
This release contains numerous rule & engine bug fixes, perf optimizations, hang fixes, community contributions and more.
You can grab this version from PowerShell Gallery @:
http://www.powershellgallery.com/packages/PSScriptAnalyzer/1.5.0
Detailed change log is here:
https://github.com/PowerShell/PSScriptAnalyzer/blob/master/CHANGELOG.MD
PSScriptAnalyzer v1.4.0
Release contains new rule to validate HelpMessage parameter attribute, rule to optimize module manifest *ToExport field values.
Reviewed and fixed the ast extents returned by rules to accurately reflect the violation, updated credential rule and singular noun rule heuristics to be more deterministic.
Release also contains numerous bug fixes to engine and default rule set.
You can grab this version from PowerShell Gallery @:
http://www.powershellgallery.com/packages/PSScriptAnalyzer/1.4.0
Detailed change log is here:
https://github.com/PowerShell/PSScriptAnalyzer/blob/master/CHANGELOG.MD
PSScriptAnalyzer v1.3.0
Release introduces the ability to run ScriptAnalyzer on platforms containing PowerShell v3 or higher.
This means PS v5 is no longer the minimum version required.
Other additions include built-in ruleset improvements based on community feedback and community rule contributions.
You can grab this version from PowerShell Gallery @:
http://www.powershellgallery.com/packages/PSScriptAnalyzer/1.3.0
Detailed change log is here:
https://github.com/PowerShell/PSScriptAnalyzer/blob/master/CHANGELOG.MD