Merge branch 'main' into addCLMRules

Author: joshcorr

Directory.Packages.props

@@ -9,8 +9,8 @@
     <PackageVersion Include="Newtonsoft.Json" Version="13.0.4" />
     <PackageVersion Include="Pluralize.NET" Version="1.0.2" />
     <PackageVersion Include="PowerShellStandard.Library" Version="5.1.1" />
-    <!-- Please update minimumPowerShellCoreVersion in PSScriptAnalyzer.psm1 when updating below SMA version for better user-facing error message -->
-    <PackageVersion Include="System.Management.Automation" Version="7.4.13" />
+    <!-- Please update minimumPowerShellCoreVersion in PSScriptAnalyzer.psm1 when updating below SMA major or minor version (but not patch) for better user-facing error message -->
+    <PackageVersion Include="System.Management.Automation" Version="7.4.14" />
     <PackageVersion Include="System.Reflection.TypeExtensions" Version="4.7.0" />
   </ItemGroup>
 </Project>

Engine/PSScriptAnalyzer.psm1

@@ -9,7 +9,8 @@ $PSModuleRoot = $PSModule.ModuleBase
 
 # Import the appropriate nested binary module based on the current PowerShell version
 $binaryModuleRoot = $PSModuleRoot
-[Version] $minimumPowerShellCoreVersion = '7.4.13'
+# This should be the equivalent of 7.4.x i.e. latest major/minor supported but lowest patch.
+[Version] $minimumPowerShellCoreVersion = '7.4.6'
 if ($PSVersionTable.PSVersion.Major -ge 6) {
     $binaryModuleRoot = Join-Path -Path $PSModuleRoot -ChildPath "PSv$($PSVersionTable.PSVersion.Major)"
     # Minimum PowerShell Core version given by PowerShell Core support itself and

README.md

@@ -66,7 +66,11 @@ documentation for the latest release is published on on learn.microsoft.com.
 ## Installation
 
 To install **PSScriptAnalyzer** from the PowerShell Gallery, see
-[Installing PSScriptAnalyzer](https://learn.microsoft.com/powershell/utility-modules/psscriptanalyzer/overview#installing-psscriptanalyzer).
+[Installing PSScriptAnalyzer](https://learn.microsoft.com/powershell/utility-modules/psscriptanalyzer/overview#installing-psscriptanalyzer) or simply open PowerShell in a Terminal and run:
+
+```powershell
+Install-Module -Name PSScriptAnalyzer
+```
 
 To install **PSScriptAnalyzer** from source code:
 

Rules/Strings.resx

@@ -1224,6 +1224,33 @@
   <data name="AvoidUsingAllowUnencryptedAuthenticationName" xml:space="preserve">
     <value>AvoidUsingAllowUnencryptedAuthentication</value>
   </data>
+  <data name="UseConsistentParameterSetNameCommonName" xml:space="preserve">
+    <value>Use Consistent Parameter Set Name</value>
+  </data>
+  <data name="UseConsistentParameterSetNameDescription" xml:space="preserve">
+    <value>Parameter set names are case-sensitive in PowerShell. This rule checks for case mismatches between DefaultParameterSetName and ParameterSetName values, case mismatches between different ParameterSetName values, and missing DefaultParameterSetName when parameter sets are used.</value>
+  </data>
+  <data name="UseConsistentParameterSetNameMissingDefaultError" xml:space="preserve">
+    <value>Param block uses parameter sets but does not specify a DefaultParameterSetName. Consider adding DefaultParameterSetName to the CmdletBinding attribute.</value>
+  </data>
+  <data name="UseConsistentParameterSetNameCaseMismatchDefaultError" xml:space="preserve">
+    <value>DefaultParameterSetName '{0}' does not match the case of ParameterSetName '{1}'. Parameter set names are case-sensitive.</value>
+  </data>
+  <data name="UseConsistentParameterSetNameCaseMismatchParameterError" xml:space="preserve">
+    <value>ParameterSetName '{0}' does not match the case of '{1}'. Parameter set names are case-sensitive and should use consistent casing.</value>
+  </data>
+  <data name="UseConsistentParameterSetNameMultipleDeclarationsError" xml:space="preserve">
+    <value>Parameter '{0}' is declared in parameter-set '{1}' multiple times.</value>
+  </data>
+  <data name="UseConsistentParameterSetNameNewLineError" xml:space="preserve">
+    <value>Parameter set names should not contain new lines.</value>
+  </data>
+  <data name="UseConsistentParameterSetNameCaseMismatchSuggestedCorrectionDescription" xml:space="preserve">
+    <value>Rename ParameterSet '{0}' to '{1}'.</value>
+  </data>
+  <data name="UseConsistentParameterSetNameName" xml:space="preserve">
+    <value>UseConsistentParameterSetName</value>
+  </data>
   <data name="AvoidReservedWordsAsFunctionNamesCommonName" xml:space="preserve">
     <value>Avoid reserved words as function names</value>
   </data>
@@ -1286,6 +1313,17 @@
   </data>
   <data name="UseConstrainedLanguageModePSCustomObjectError" xml:space="preserve">
     <value>[PSCustomObject]@{{}} syntax is not permitted in Constrained Language Mode. Use New-Object PSObject -Property @{{}} or plain hashtables instead.</value>
+  <data name="UseSingleValueFromPipelineParameterCommonName" xml:space="preserve">
+    <value>Use a single ValueFromPipeline parameter per parameter set</value>
+  </data>
+  <data name="UseSingleValueFromPipelineParameterDescription" xml:space="preserve">
+    <value>Use at most a single ValueFromPipeline parameter per parameter set to avoid undefined or unexpected behaviour.</value>
+  </data>
+  <data name="UseSingleValueFromPipelineParameterError" xml:space="preserve">
+    <value>Multiple parameters ({0}) in parameter set '{1}' are marked as ValueFromPipeline. Only one parameter per parameter set should accept pipeline input.</value>
+  </data>
+  <data name="UseSingleValueFromPipelineParameterName" xml:space="preserve">
+    <value>UseSingleValueFromPipelineParameter</value>
   </data>
   <data name="UseConsistentParametersKindCommonName" xml:space="preserve">
     <value>Use correct function parameters definition kind.</value>
@@ -1302,4 +1340,4 @@
   <data name="UseConsistentParametersKindParamBlockError" xml:space="preserve">
     <value>Use inline parameters definition instead of param() block in function body.</value>
   </data>
-</root>
+</root>