Skip to content

Prepare release v1.14.0 #773

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
kapilmb merged 3 commits into from
Jun 9, 2017
Merged

Prepare release v1.14.0 #773

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
d8d8fe7
Update changelog
Jun 9, 2017
d7f45a1
Update module manifest
Jun 9, 2017
07db688
Update version in project.json files
Jun 9, 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
11 changes: 10 additions & 1 deletion CHANGELOG.MD
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,13 @@
## [1.13.0](https://github.com/PowerShell/PSScriptAnalyzer/tree/1.13.0) - 2017-05-18
## [1.14.0](https://github.com/PowerShell/PSScriptAnalyzer/tree/1.14.0) - 2017-06-09

### Added
- (#772) [`Invoke-Formatter`](https://github.com/PowerShell/PSScriptAnalyzer/blob/4f47ef95edd045029628ba9a4079b1dda19f080f/docs/markdown/Invoke-Formatter.md) cmdlet to format PowerShell scripts. The cmdlet takes a script string and a settings file and outputs formatted script string based on the provided settings. If no settings are provided, the formatter uses the default `CodeFormatting` settings, which can be found at `Settings/CodeFormatting.psd1`.

### Fixed
- (#770) `PSUseIdenticalMandatoryParametersForDSC` rule violation extent. The violation extent covers only the relevant function name, which prior the fix would mark the entire script. This prevented rule suppression from working when the suppression is declared inside `Get/Set/Test` functions.
- (#770) `PSUseIdenticalMandatoryParametersForDSC` behavior to look for mandatory parameters in `Get/Set/Test` functions in a script based resource only if they are declared with attributes, `Key` or `Required`, in the corresponding `mof` file.

## [1.13.0](https://github.com/PowerShell/PSScriptAnalyzer/tree/1.13.0) - 2017-05-18

### Added
- [`PSUseSupportsShouldProcess`](https://github.com/PowerShell/PSScriptAnalyzer/blob/f92dabdef61b87d5f9f9f2140739c9f3f210b2d8/RuleDocumentation/UseSupportsShouldProcess.md) rule to discourage manual `whatif` and `confirm` parameter declarations.
Expand Down
13 changes: 6 additions & 7 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.13.0'
ModuleVersion = '1.14.0'

# ID used to uniquely identify this module
GUID = 'd6245802-193d-4068-a631-8863a4342a18'
Expand Down Expand Up @@ -88,14 +88,11 @@ PrivateData = @{
IconUri = ''
ReleaseNotes = @'
### Added
- `PSUseSupportsShouldProcess` rule to discourage manual `whatif` and `confirm` parameter declarations.
- Suggested corrections to `PSProvideCommentHelp` rule. The rule can now be configured to:
- trigger on non-exported functions. But by default, the rule triggers only on exported functions that do have comment help.
- place the suggested corrections either before a function definition, or at the beginning or end of a function's body.
- choose between block comment or line comment style of suggested comment help correction.
- (#772) `Invoke-Formatter` cmdlet to format PowerShell scripts. The cmdlet takes a script string and a settings file and outputs formatted script string based on the provided settings. If no settings are provided, the formatter uses the default `CodeFormatting` settings, which can be found at `Settings/CodeFormatting.psd1`.

### Fixed
- `PSAlignAssignmentStatement` to align assignment statements in DSC configurations that have *Undefined DSC Resource* parse errors.
- (#770) `PSUseIdenticalMandatoryParametersForDSC` rule violation extent. The violation extent covers only the relevant function name, which prior the fix would mark the entire script. This prevented rule suppression from working when the suppression is declared inside `Get/Set/Test` functions.
- (#770) `PSUseIdenticalMandatoryParametersForDSC` behavior to look for mandatory parameters in `Get/Set/Test` functions in a script based resource only if they are declared with attributes, `Key` or `Required`, in the corresponding `mof` file.
'@
}
}
Expand All @@ -115,3 +112,5 @@ 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.13.0",
"version": "1.14.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.13.0",
"version": "1.14.0",
"dependencies": {
"System.Management.Automation": "6.0.0-alpha13",
"Engine": "1.13.0",
"Engine": "1.14.0",
"Newtonsoft.Json": "9.0.1"
},

Expand Down