M⚠️ ◾ Automated Package Update by neilr81 · Pull Request #824 · microsoft/Omex

neilr81 · 2026-02-08T21:46:53Z

This PR was created automatically by the workflow run 21805928402.

This script updates NuGet package versions in the Directory.Packages.props file by querying the latest available versions and updating the Version attributes accordingly, while respecting the PreserveMajor attribute and pre-release version detection.

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Changed the trigger for package updates to a scheduled cron job.

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

* Initial plan * Gate PR creation on changes detection flag Co-authored-by: neilr81 <49037171+neilr81@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: neilr81 <49037171+neilr81@users.noreply.github.com>

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Removed GitHub CLI installation step from workflow.

Removed the 'powershell' label from the automated package update PR.

This script updates .NET SDK and MSBuild SDK versions in the global.json file by querying the latest releases and modifying the file accordingly.

github-actions · 2026-02-08T21:47:09Z

PR Metrics

❌ Try to keep pull requests smaller than 400 lines of new product code by following the Single Responsibility Principle (SRP).
⚠️ Consider adding additional tests.

	Lines
Product Code	709
Test Code	-
Subtotal	709
Ignored Code	68
Total	777

Metrics computed by PR Metrics. Add it to your Azure DevOps and GitHub PRs!

Copilot

Pull request overview

Automates dependency maintenance by adding a GitHub Actions workflow and PowerShell scripts to update centrally-managed NuGet package versions (and SDK versions), plus applies an automated package version bump in Directory.Packages.props.

Changes:

Bump MSTest package versions in Directory.Packages.props and normalize XML formatting.
Add a scheduled GitHub Actions workflow to run package update automation and open a PR.
Add PowerShell automation scripts to update NuGet package versions and .NET SDK/MSBuild SDK versions.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 7 comments.

File	Description
Directory.Packages.props	Updates MSTest versions and reformats PackageVersion entries.
.github/workflows/package-update.yml	Adds a scheduled automation workflow that runs update script and opens a PR.
.github/scripts/Update-NuGetPackageVersions.ps1	Adds script to search latest package versions and update `Directory.Packages.props` AutoUpdate groups.
.github/scripts/Update-DotNetSdkVersions.ps1	Adds script to update `global.json` SDK/MSBuild SDK versions.

Copilot · 2026-02-08T21:51:43Z

+on:
+  schedule:
+    - cron: "0 6 * * 1"
+  pull_request:
+    branches: [ "main" ]


The workflow is configured to run on pull_request events and can create/push a new branch + open a PR. This is likely to spam PRs and can recurse when the automation PR itself triggers the workflow. Limit this workflow to schedule (and optionally workflow_dispatch) rather than pull_request.

Copilot · 2026-02-08T21:51:43Z

+        # Prefer NuGet-GitHub.Config (used on GitHub runners) when present, otherwise fall back to NuGet.config
+        $nugetGithubConfigPath = Join-Path $SourcesDirectory "NuGet-GitHub.Config"
+        $nugetConfigPath = Join-Path $SourcesDirectory "NuGet.config"
+        $configSourceFlag = ""


The repo root uses NuGet.Config (capital C), but the script looks for NuGet.config. On case-sensitive filesystems this will never be found, so the intended feeds/config won’t be used. Update this to match the repo’s filename (or check both casings).

Copilot · 2026-02-08T21:51:43Z

+        $response = Invoke-WebRequest -Uri $sdkRedirectUrl -Method HEAD -MaximumRedirection 10 -UseBasicParsing
+
+        if ($EnableVerboseLogging) {
+            Write-Host "  [VERBOSE] Response status: $($response.StatusCode)"
+            Write-Host "  [VERBOSE] Response headers: $($response.Headers | ConvertTo-Json -Compress)"
+        }
+
+        # PowerShell Core: Get final URL from response object
+        $finalUrl = $response.BaseResponse.RequestMessage.RequestUri.AbsoluteUri


Invoke-WebRequest result handling is not compatible across Windows PowerShell 5.1 vs PowerShell Core: -UseBasicParsing is legacy, and $response.BaseResponse.RequestMessage.RequestUri is not available on WinPS 5.1. If this script is intended for Azure Pipelines (often WinPS 5.1), use a response URI property that exists there (e.g., BaseResponse.ResponseUri) and avoid -UseBasicParsing.

Suggested change

$response = Invoke-WebRequest -Uri $sdkRedirectUrl -Method HEAD -MaximumRedirection 10 -UseBasicParsing

if ($EnableVerboseLogging) {

Write-Host " [VERBOSE] Response status: $($response.StatusCode)"

Write-Host " [VERBOSE] Response headers: $($response.Headers | ConvertTo-Json -Compress)"

}

# PowerShell Core: Get final URL from response object

$finalUrl = $response.BaseResponse.RequestMessage.RequestUri.AbsoluteUri

$response = Invoke-WebRequest -Uri $sdkRedirectUrl -Method HEAD -MaximumRedirection 10

if ($EnableVerboseLogging) {

Write-Host " [VERBOSE] Response status: $($response.StatusCode)"

Write-Host " [VERBOSE] Response headers: $($response.Headers | ConvertTo-Json -Compress)"

}

# Get final URL from response object (compatible with Windows PowerShell 5.1 and PowerShell Core)

$finalUrl = $response.BaseResponse.ResponseUri.AbsoluteUri

Copilot · 2026-02-08T21:51:43Z

+    if ($firstVersionObject.Version -eq $secondVersionObject.Version) {
+        if (-not $firstVersionObject.Suffix) { return $First }
+        if (-not $secondVersionObject.Suffix) { return $Second }
+        if ($firstVersionObject.Suffix -lt $secondVersionObject.Suffix) { return $Second }
+        return $First


Get-LatestVersionFromString compares pre-release suffixes lexicographically (string compare). This gives incorrect ordering for versions like -preview.10 vs -preview.2, which can cause the script to select the wrong "latest" version. Consider using a SemVer/NuGetVersion-aware comparison (or parsing numeric components of the suffix) instead of plain string comparison.

Copilot · 2026-02-08T21:51:44Z

+    if ($firstVersionObject.Version -eq $secondVersionObject.Version) {
+        if (-not $firstVersionObject.Suffix) { return $First }
+        if (-not $secondVersionObject.Suffix) { return $Second }
+        if ($firstVersionObject.Suffix -lt $secondVersionObject.Suffix) { return $Second }
+        return $First
+    }


Get-LatestVersionFromString compares pre-release suffixes lexicographically (string compare), which can order -preview.10 before -preview.2. This can select the wrong latest SDK/MSBuild SDK version when pre-releases are involved. Use a SemVer/NuGetVersion-aware comparison (or parse numeric suffix parts) instead.

Copilot · 2026-02-08T21:51:44Z

+    [Parameter(Mandatory = $false)]
+    [bool]$FailOnError = $false
+)
+


$SourcesDirectory defaults to $env:BUILD_SOURCESDIRECTORY but the script doesn’t normalize/validate it like the package update script does. If the env var is unset/empty, Join-Path will fail. Add the same fallback logic (e.g., $env:GITHUB_WORKSPACE then Get-Location) and validate the directory exists.

Suggested change

# Normalize and validate the sources directory to avoid Join-Path failures

if ([string]::IsNullOrWhiteSpace($SourcesDirectory)) {

if (-not [string]::IsNullOrWhiteSpace($env:BUILD_SOURCESDIRECTORY)) {

$SourcesDirectory = $env:BUILD_SOURCESDIRECTORY

} elseif (-not [string]::IsNullOrWhiteSpace($env:GITHUB_WORKSPACE)) {

$SourcesDirectory = $env:GITHUB_WORKSPACE

} else {

$SourcesDirectory = (Get-Location).Path

}

}

try {

# Resolve to a full, normalized path and ensure it exists as a directory

$resolvedSourcesDirectory = Resolve-Path -Path $SourcesDirectory -ErrorAction Stop

if (-not (Test-Path -Path $resolvedSourcesDirectory -PathType Container)) {

throw "Sources directory '$SourcesDirectory' is not a valid directory."

}

$SourcesDirectory = $resolvedSourcesDirectory.ProviderPath

}

catch {

$message = "Failed to resolve sources directory from '$SourcesDirectory'."

if ($FailOnError) {

throw "$message Error: $($_.Exception.Message)"

} else {

Write-Warning "$message Falling back to current location."

$fallback = (Get-Location).Path

$SourcesDirectory = $fallback

}

}

Copilot · 2026-02-08T21:51:44Z

+        # Check if NuGet.config exists in the sources directory
+        $nugetConfigPath = Join-Path $SourcesDirectory "NuGet.config"
+        $configSourceFlag = ""
+        if (Test-Path $nugetConfigPath) {
+            $configSourceFlag = "--configfile `"$nugetConfigPath`""
+            if ($EnableVerboseLogging) {
+                Write-Host "  [VERBOSE] Using NuGet.config from: $nugetConfigPath"
+            }
+        } else {
+            Write-Warning "NuGet.config not found at: $nugetConfigPath - search may not find private feeds"


The repo root uses NuGet.Config (capital C), but this script looks for NuGet.config. On case-sensitive filesystems the config won’t be found, so package searches may miss required feeds. Update the filename (or check both casings).

Suggested change

# Check if NuGet.config exists in the sources directory

$nugetConfigPath = Join-Path $SourcesDirectory "NuGet.config"

$configSourceFlag = ""

if (Test-Path $nugetConfigPath) {

$configSourceFlag = "--configfile `"$nugetConfigPath`""

if ($EnableVerboseLogging) {

Write-Host " [VERBOSE] Using NuGet.config from: $nugetConfigPath"

}

} else {

Write-Warning "NuGet.config not found at: $nugetConfigPath - search may not find private feeds"

# Check if NuGet.config / NuGet.Config exists in the sources directory

$nugetConfigLower = Join-Path $SourcesDirectory "NuGet.config"

$nugetConfigUpper = Join-Path $SourcesDirectory "NuGet.Config"

$configSourceFlag = ""

$nugetConfigPath = $null

if (Test-Path $nugetConfigLower) {

$nugetConfigPath = $nugetConfigLower

} elseif (Test-Path $nugetConfigUpper) {

$nugetConfigPath = $nugetConfigUpper

}

if ($nugetConfigPath) {

$configSourceFlag = "--configfile `"$nugetConfigPath`""

if ($EnableVerboseLogging) {

Write-Host " [VERBOSE] Using NuGet config from: $nugetConfigPath"

}

} else {

Write-Warning "NuGet config file not found (checked: $nugetConfigLower, $nugetConfigUpper) - search may not find private feeds"

neilr81 and others added 30 commits February 7, 2026 14:08

Add GitHub Actions workflow for package updates

5a23446

Update script paths in package-update.yml

c0d9eb7

Apply suggestion from @Copilot

bfb26c8

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Update package-update workflow to use cron schedule

88eb82c

Changed the trigger for package updates to a scheduled cron job.

Update .github/scripts/Update-NuGetPackageVersions.ps1

671dd97

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Update .github/scripts/Update-NuGetPackageVersions.ps1

4b27d31

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Apply suggestion from @Copilot

8c3190a

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Apply suggestion from @Copilot

287fbe0

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Apply suggestion from @Copilot

c56db37

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Add pull_request_target trigger to workflow

1a02929

Apply suggestion from @Copilot

1cf02c9

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Update package-update.yml

331b09d

Update package-update.yml

07d2d47

Rename checkout step for clarity

0455764

Remove GitHub CLI installation from package-update.yml

1cbd892

Removed GitHub CLI installation step from workflow.

Update Update-NuGetPackageVersions.ps1

3e92781

Fix label assignment in package-update workflow

fc9b6c7

Remove 'powershell' label from package update PR

527230e

Removed the 'powershell' label from the automated package update PR.

Add label to automated package update PR

34493b9

Fix label formatting in package-update.yml

f2afff8

Add token input for create pull request action

f5431d8

Update GH_TOKEN to use secrets for PR creation

cd5081d

Update package-update.yml

852325b

Add script to update .NET SDK and MSBuild SDK versions

0150f4e

This script updates .NET SDK and MSBuild SDK versions in the global.json file by querying the latest releases and modifying the file accordingly.

Merge 0150f4e into 60e2378

6c0ff0c

chore(automation): apply PowerShell updates

3d8c054

Merge 3d8c054 into 60e2378

7d85dac

Merge 7d85dac into 60e2378

2e990e3

neilr81 added 9 commits February 8, 2026 21:33

Merge 2e990e3 into 60e2378

3188132

Merge 3188132 into 60e2378

d9a33c9

Merge d9a33c9 into 60e2378

de397b9

Merge de397b9 into 60e2378

483c42f

Merge 483c42f into 60e2378

46a3008

Merge 46a3008 into 60e2378

ef098de

Merge ef098de into 60e2378

c062660

Merge c062660 into 60e2378

4ab4a26

Merge 4ab4a26 into 60e2378

2fdd9c4

neilr81 requested a review from a team as a code owner February 8, 2026 21:46

neilr81 added the automation Item has been created automatically. label Feb 8, 2026

Copilot AI review requested due to automatic review settings February 8, 2026 21:46

neilr81 self-assigned this Feb 8, 2026

neilr81 added the automation Item has been created automatically. label Feb 8, 2026

github-actions Bot changed the title ~~Automated Package Update~~ M⚠️ ◾ Automated Package Update Feb 8, 2026

Copilot started reviewing on behalf of neilr81 February 8, 2026 21:47 View session

neilr81 closed this Feb 8, 2026

neilr81 deleted the automation/package-update-21805928402 branch February 8, 2026 21:48

Copilot AI reviewed Feb 8, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

M⚠️ ◾ Automated Package Update#824

M⚠️ ◾ Automated Package Update#824
neilr81 wants to merge 39 commits into
mainfrom
automation/package-update-21805928402

neilr81 commented Feb 8, 2026

Uh oh!

github-actions Bot commented Feb 8, 2026

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI Feb 8, 2026

Uh oh!

Copilot AI Feb 8, 2026

Uh oh!

Copilot AI Feb 8, 2026

Uh oh!

Copilot AI Feb 8, 2026

Uh oh!

Copilot AI Feb 8, 2026

Uh oh!

Copilot AI Feb 8, 2026

Uh oh!

Copilot AI Feb 8, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

+# Normalize and validate the sources directory to avoid Join-Path failures
+if ([string]::IsNullOrWhiteSpace($SourcesDirectory)) {
+    if (-not [string]::IsNullOrWhiteSpace($env:BUILD_SOURCESDIRECTORY)) {
+        $SourcesDirectory = $env:BUILD_SOURCESDIRECTORY
+    } elseif (-not [string]::IsNullOrWhiteSpace($env:GITHUB_WORKSPACE)) {
+        $SourcesDirectory = $env:GITHUB_WORKSPACE
+    } else {
+        $SourcesDirectory = (Get-Location).Path
+    }
+}
+try {
+    # Resolve to a full, normalized path and ensure it exists as a directory
+    $resolvedSourcesDirectory = Resolve-Path -Path $SourcesDirectory -ErrorAction Stop
+    if (-not (Test-Path -Path $resolvedSourcesDirectory -PathType Container)) {
+        throw "Sources directory '$SourcesDirectory' is not a valid directory."
+    }
+    $SourcesDirectory = $resolvedSourcesDirectory.ProviderPath
+}
+catch {
+    $message = "Failed to resolve sources directory from '$SourcesDirectory'."
+    if ($FailOnError) {
+        throw "$message Error: $($_.Exception.Message)"
+    } else {
+        Write-Warning "$message Falling back to current location."
+        $fallback = (Get-Location).Path
+        $SourcesDirectory = $fallback
+    }
+}

Conversation

neilr81 commented Feb 8, 2026

Uh oh!

github-actions Bot commented Feb 8, 2026

PR Metrics

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Feb 8, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 8, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 8, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 8, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 8, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 8, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 8, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants