diff --git a/CHANGELOG.MD b/CHANGELOG.MD
index d1012064c..a135467d7 100644
--- a/CHANGELOG.MD
+++ b/CHANGELOG.MD
@@ -1,4 +1,11 @@
-## [1.14.0](https://github.com/PowerShell/PSScriptAnalyzer/tree/1.14.0) - 2017-06-09
+## [1.14.1](https://github.com/PowerShell/PSScriptAnalyzer/tree/1.14.1) - 2017-06-12
+
+### Fixed
+- (#777) `Invoke-Formatter`
+    - Make the cmdlet parameters positional.
+    - Updated documentation so that `Get-Help Invoke-Formatter -Syntax` returns a valid syntax.
+
+## [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`.
diff --git a/Engine/PSScriptAnalyzer.psd1 b/Engine/PSScriptAnalyzer.psd1
index 9c25d9c73..3e34f3672 100644
--- a/Engine/PSScriptAnalyzer.psd1
+++ b/Engine/PSScriptAnalyzer.psd1
@@ -11,7 +11,7 @@ Author = 'Microsoft Corporation'
 RootModule = 'PSScriptAnalyzer.psm1'
 
 # Version number of this module.
-ModuleVersion = '1.14.0'
+ModuleVersion = '1.14.1'
 
 # ID used to uniquely identify this module
 GUID = 'd6245802-193d-4068-a631-8863a4342a18'
@@ -87,12 +87,10 @@ PrivateData = @{
         ProjectUri = 'https://github.com/PowerShell/PSScriptAnalyzer'
         IconUri = ''
         ReleaseNotes = @'
-### Added
-- (#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
-- (#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.
+- (#777) `Invoke-Formatter`
+    - Make the cmdlet parameters positional.
+    - Updated documentation so that `Get-Help Invoke-Formatter -Syntax` returns a valid syntax.
 '@
     }
 }
@@ -114,3 +112,4 @@ PrivateData = @{
 
 
 
+
diff --git a/Engine/project.json b/Engine/project.json
index 2403557c6..d5cf0a8b9 100644
--- a/Engine/project.json
+++ b/Engine/project.json
@@ -1,6 +1,6 @@
 {
   "name": "Microsoft.Windows.PowerShell.ScriptAnalyzer",
-  "version": "1.14.0",
+  "version": "1.14.1",
   "dependencies": {
 "System.Management.Automation": "6.0.0-alpha13"
     },
diff --git a/Rules/project.json b/Rules/project.json
index e40d2beff..4575dc07e 100644
--- a/Rules/project.json
+++ b/Rules/project.json
@@ -1,9 +1,9 @@
 {
   "name": "Microsoft.Windows.PowerShell.ScriptAnalyzer.BuiltinRules",
-  "version": "1.14.0",
+  "version": "1.14.1",
   "dependencies": {
     "System.Management.Automation": "6.0.0-alpha13",
-    "Engine": "1.14.0",
+    "Engine": "1.14.1",
     "Newtonsoft.Json": "9.0.1"
   },