Merge pull request #719 from PowerShell/kapilmb/v1.11.0

Prepare release v1.11.0

Author: Kapil Borle

CHANGELOG.MD

@@ -1,17 +1,22 @@
-## unreleased
-
+## [1.11.0](https://github.com/PowerShell/PSScriptAnalyzer/tree/1.11.0) - 2017-03-01
 ### Added
-- Built-in settings presets to specify settings from command line. Currently, PSSA ships with `PSGallery`, `CodeFormatting`, `DSC`, and other setting presets. All of them can be found in the `Settings/` directory in the module. To use them just pass them as an argument to the `Settings` parameters. For example, if you want to run rules that *powershellgallery* runs, then use the following command.
+- Built-in settings presets to specify settings from command line (#717). Currently, PSSA ships with `PSGallery`, `CodeFormatting`, `DSC`, and other settings presets. All of them can be found in the `Settings/` directory in the module. To use them just pass them as an argument to the `Settings` parameter. For example, if you want to run rules that *powershellgallery* runs, then use the following command.
 ```powershell
 PS> Invoke-ScriptAnalyzer -Path /path/to/your/module -Settings PSGallery
 ```
-- Argument completion for built-in settings presets.
-- Argument completion for `IncludeRule` and `ExcludeRule` parameters.
+- Argument completion for built-in settings presets (#717).
+- Argument completion for `IncludeRule` and `ExcludeRule` parameters (#717).
+- Option to `PSCloseBrace` rule to add new line after the brace (#713).
+- Option to `PSCloseBrace` rule to ignore expressions that have open and close braces on the same line (#706).
+- New rule, [PSUseConsistentWhitespace](https://github.com/PowerShell/PSScriptAnalyzer/blob/9a6fe537c11c9c8d7ed872a7464eb192cab00883/RuleDocumentation/UseConsistentWhitespace.md), to check for whitespace style around operators and separators (#702).
 
 ### Fixed
+- Indentation when pipes precede new lines in a multi-line command expression in `PSUseConsistentIdentation` rule (#705).
+- Handling of SubExpressionAsts (`$(...)`) in `PSUseConsistentIdentation` rule (#700).
+- Performance issues caused by `get-command` cmdlet (#695).
 
 ### Changed
-    - Settings implementation to decouple it from engine.
+- Settings implementation to decouple it from engine (#717).
 
 ## [1.10.0](https://github.com/PowerShell/PSScriptAnalyzer/tree/1.10.0) - 2017-01-19
 ### Added

Engine/PSScriptAnalyzer.psd1

@@ -11,7 +11,7 @@ Author = 'Microsoft Corporation'
 RootModule = 'PSScriptAnalyzer.psm1'
 
 # Version number of this module.
-ModuleVersion = '1.10.0'
+ModuleVersion = '1.11.0'
 
 # ID used to uniquely identify this module
 GUID = 'd6245802-193d-4068-a631-8863a4342a18'
@@ -88,22 +88,23 @@ PrivateData = @{
         IconUri = ''
         ReleaseNotes = @'
 ### Added
-- Three rules to enable code formatting feature in vscode (#690)
-    - PSPlaceOpenBrace
-    - PSPlaceCloseBrace
-    - PSUseConsistentIdentation
+- Built-in settings presets to specify settings from command line (#717). Currently, PSSA ships with `PSGallery`, `CodeFormatting`, `DSC`, and other settings presets. All of them can be found in the `Settings/` directory in the module. To use them just pass them as an argument to the `Settings` parameter. For example, if you want to run rules that *powershellgallery* runs, then use the following command.
+```powershell
+PS> Invoke-ScriptAnalyzer -Path /path/to/your/module -Settings PSGallery
+```
+- Argument completion for built-in settings presets (#717).
+- Argument completion for `IncludeRule` and `ExcludeRule` parameters (#717).
+- Option to `PSCloseBrace` rule to add new line after the brace (#713).
+- Option to `PSCloseBrace` rule to ignore expressions that have open and close braces on the same line (#706).
+- New rule, PSUseConsistentWhitespace, to check for whitespace style around operators and separators (#702).
 
 ### Fixed
-- `PSProvideCommentHelp` violation extent (#679)
-- `PSAvoidUsingCmdletAliases` rule
-    + false positives in DSC configurations (#678)
-    + violation extent (#685)
-- `PSDSCDSCTestsPresent` rule to check for tests in subdirectories
-- `PSUsePSCredentialType` rule (#683)
-    + trigger only if invoked from PS version 4 and below
-    + violation extent
-- `PSAvoidUsingComputerNameHardcoded` rule to ignore `localhost` (#687)
-- Performance issues caused by invoking `get-command` method (#692)
+- Indentation when pipes precede new lines in a multi-line command expression in `PSUseConsistentIdentation` rule (#705).
+- Handling of SubExpressionAsts (`$(...)`) in `PSUseConsistentIdentation` rule (#700).
+- Performance issues caused by `get-command` cmdlet (#695).
+
+### Changed
+- Settings implementation to decouple it from engine (#717).
 '@
     }
 }
@@ -119,3 +120,4 @@ PrivateData = @{
 
 
 
+

Engine/project.json

@@ -1,6 +1,6 @@
 {
   "name": "Microsoft.Windows.PowerShell.ScriptAnalyzer",
-  "version": "1.10.0",
+  "version": "1.11.0",
   "dependencies": {
 "System.Management.Automation": "1.0.0-alpha12"
     },

Rules/project.json

@@ -1,9 +1,9 @@
 {
   "name": "Microsoft.Windows.PowerShell.ScriptAnalyzer.BuiltinRules",
-  "version": "1.10.0",
+  "version": "1.11.0",
   "dependencies": {
     "System.Management.Automation": "1.0.0-alpha12",
-    "Engine": "1.10.0",
+    "Engine": "1.11.0",
     "Newtonsoft.Json": "9.0.1"
   },