Skip to content

Prepare release v1.15.0 #792

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jun 21, 2017
Merged

Prepare release v1.15.0 #792

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
bb68c03
Update changelog
Jun 21, 2017
0cb408f
Update module manifest
Jun 21, 2017
c11c73d
Update version in project.json files
Jun 21, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 13 additions & 1 deletion CHANGELOG.MD
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,16 @@
## [1.14.1](https://github.com/PowerShell/PSScriptAnalyzer/tree/1.14.1) - 2017-06-12
## [1.15.0](https://github.com/PowerShell/PSScriptAnalyzer/tree/1.15.0) - 2017-06-21

### Added
- (#780) `Range` parameter to the `Invoke-Formatter` cmdlet. The user can specify the range in which formatting should be applied. The primary usage for this parameter is to be used with editors that request selection formatting.
- (#782, #788) Allman style, Stroustrup style and one true brace style (OTBS) code formatting presets.
- (#790) `Kind` switch to `PSUseConsistentIndentation` rule to provide tabbed indentation.

### Fixed
- (#781, #784) `NewLineAfer` switch behavior in `PSPlaceCloseBrace` rule. When the switch is set to `$false`, the emitted suggested corrections enforce branching control statements to be on the same line as their preceding closing braces. On the other hand when the switch is set to `$true`, the emitted suggested corrections enforce branching controls statements to be on the next line.

Many thanks to @rkeithhill for contributing the _Stroustrup_ style code formatting preset.

## [1.14.1](https://github.com/PowerShell/PSScriptAnalyzer/tree/1.14.1) - 2017-06-12

### Fixed
- (#777) `Invoke-Formatter`
Expand Down
14 changes: 10 additions & 4 deletions Engine/PSScriptAnalyzer.psd1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ Author = 'Microsoft Corporation'
RootModule = 'PSScriptAnalyzer.psm1'

# Version number of this module.
ModuleVersion = '1.14.1'
ModuleVersion = '1.15.0'

# ID used to uniquely identify this module
GUID = 'd6245802-193d-4068-a631-8863a4342a18'
Expand Down Expand Up @@ -87,10 +87,15 @@ PrivateData = @{
ProjectUri = 'https://github.com/PowerShell/PSScriptAnalyzer'
IconUri = ''
ReleaseNotes = @'
### Added
- (#780) `Range` parameter to the `Invoke-Formatter` cmdlet. The user can specify the range in which formatting should be applied. The primary usage for this parameter is to be used with editors that request selection formatting.
- (#782, #788) Allman style, Stroustrup style and one true brace style (OTBS) code formatting presets.
- (#790) `Kind` switch to `PSUseConsistentIndentation` rule to provide tabbed indentation.

### Fixed
- (#777) `Invoke-Formatter`
- Make the cmdlet parameters positional.
- Updated documentation so that `Get-Help Invoke-Formatter -Syntax` returns a valid syntax.
- (#781, #784) `NewLineAfer` switch behavior in `PSPlaceCloseBrace` rule. When the switch is set to `$false`, the emitted suggested corrections enforce branching control statements to be on the same line as their preceding closing braces. On the other hand when the switch is set to `$true`, the emitted suggested corrections enforce branching controls statements to be on the next line.

Many thanks to @rkeithhill for contributing the _Stroustrup_ style code formatting preset.
'@
}
}
Expand All @@ -113,3 +118,4 @@ PrivateData = @{




2 changes: 1 addition & 1 deletion Engine/project.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "Microsoft.Windows.PowerShell.ScriptAnalyzer",
"version": "1.14.1",
"version": "1.15.0",
"dependencies": {
"System.Management.Automation": "6.0.0-alpha13"
},
Expand Down
4 changes: 2 additions & 2 deletions Rules/project.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
{
"name": "Microsoft.Windows.PowerShell.ScriptAnalyzer.BuiltinRules",
"version": "1.14.1",
"version": "1.15.0",
"dependencies": {
"System.Management.Automation": "6.0.0-alpha13",
"Engine": "1.14.1",
"Engine": "1.15.0",
"Newtonsoft.Json": "9.0.1"
},

Expand Down