Update .NET SDK, PowerShell SDK dependencies

[Copilot]

Follows the established pattern from commit aa2180a ("Update .NET SDK, PowerShell SDK, and Newtonsoft.Json").

Changes

• System.Management.Automation: 7.4.13 → 7.4.14 (latest 7.4.x patch)
• minimumPowerShellCoreVersion in Engine/PSScriptAnalyzer.psm1: '7.4.13' → '7.4.14' (kept aligned with SMA version per the in-code comment)
• .NET SDK in global.json: 8.0.416 → 8.0.419

Not updated (with rationale)

Package	Current	Latest	Reason skipped
Newtonsoft.Json	13.0.4	13.0.4	Already at latest
Microsoft.Management.Infrastructure	3.0.0	4.0.0	Major version bump — outside the conservative patch-update pattern
Microsoft.CSharp	4.7.0	4.7.0	Already at latest
Microsoft.Win32.Registry	5.0.0	5.0.0	Already at latest
System.Reflection.TypeExtensions	4.7.0	4.7.0	Already at latest
PowerShellStandard.Library	5.1.1	5.1.1	Already at latest
Pluralize.NET	1.0.2	1.0.2	Already at latest

[Copilot]

Pull request overview

This PR updates pinned toolchain and dependency versions to the latest patch releases, keeping the System.Management.Automation (SMA) NuGet reference aligned with the PowerShell minimum version gate used by the PSScriptAnalyzer module loader.

Changes:

• Bump .NET SDK in global.json from 8.0.416 to 8.0.419.
• Bump System.Management.Automation from 7.4.13 to 7.4.14.
• Update minimumPowerShellCoreVersion to 7.4.14 to stay consistent with the SMA version.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
global.json	Updates the pinned .NET SDK patch version used by the repo.
Engine/PSScriptAnalyzer.psm1	Keeps the PowerShell minimum supported version check aligned with the SMA package version.
Directory.Packages.props	Updates the centrally-managed SMA package version to 7.4.14.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[andyleejordan]

Perhaps premature, the GitHub Actions images don't even have PowerShell 7.4.14 yet:

VERBOSE: Testing with PowerShell 7.4.13
Exception: Minimum supported version of PSScriptAnalyzer for PowerShell Core is 7.4.14 but current version is '7.4.13'. Please update PowerShell Core.

[bergmeister]

happy with it but doesn't make any difference since we use latest feature (8.0.x) anyway as per below rollForward setting

[andyleejordan]

HAHAHA yes I agree but the people who maintain internal tools that check this file don't seem to understand that.

[bergmeister]

Perhaps premature, the GitHub Actions images don't even have PowerShell 7.4.14 yet:

VERBOSE: Testing with PowerShell 7.4.13
Exception: Minimum supported version of PSScriptAnalyzer for PowerShell Core is 7.4.14 but current version is '7.4.13'. Please update PowerShell Core.

that's ok, can do later as well. in the end it's just a reference, we don't ship SMA so whatever PowerShell patch version they are using, it's up to user to use latest patched version within 30 days after new release anyway if they want to stay supported so we don't necessarily have to enforce it too much. With 1 year release cycles, a few PS patches happen anyway