Fix mgmt library regeneration in Submit-AzureSdkForNetPr.ps1

[Copilot]

The regen preview pipeline aborted mgmt library regeneration with Unbranded package not found: .../csharp-debug-.../typespec-http-client-csharp-<version>.tgz.

Update-MgmtGenerator resolves the unbranded emitter from the debug folder as typespec-http-client-csharp-$LocalVersion.tgz, but Submit-AzureSdkForNetPr.ps1 referenced the unbranded .tgz directly from $BuildArtifactsPath and only staged the .nupkg files and the locally built Azure .tgz into the debug folder — leaving the unbranded package absent from where the mgmt build looks.

Changes

• Submit-AzureSdkForNetPr.ps1: Copy the unbranded typespec-http-client-csharp-*.tgz from build artifacts into $debugFolder and point $unbrandedPackagePath at that copy, so both the Azure and management plane generators resolve it from the same location.

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
1 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@typespec/http-client-csharp@11319

commit: 2c631b9

[Copilot]

Pull request overview

This PR fixes management library regeneration in Submit-AzureSdkForNetPr.ps1 by ensuring the unbranded @typespec/http-client-csharp .tgz is staged into the same debug folder used by RegenPreview’s generator update flow, aligning Azure + mgmt regeneration to resolve local packages from a consistent location.

Changes:

• Copies the unbranded typespec-http-client-csharp-*.tgz from $BuildArtifactsPath into $debugFolder.
• Updates $unbrandedPackagePath to point at the staged copy in $debugFolder.

[Copilot]

Pull request overview

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

Comments suppressed due to low confidence (1)

packages/http-client-csharp/eng/scripts/Submit-AzureSdkForNetPr.ps1:484

• $unbrandedTgz is selected with Select-Object -First 1 from typespec-http-client-csharp-*.tgz. If the build artifacts contain multiple unbranded emitter packages (e.g., from multiple runs/versions), this can silently pick the wrong .tgz and then rename it to ...-$PackageVersion.tgz, causing the regen to use a different emitter version than requested. Prefer selecting the .tgz that matches $PackageVersion and throw with a diagnostic list when it’s missing.

                $unbrandedTgz = Get-ChildItem -Path $BuildArtifactsPath -Filter "typespec-http-client-csharp-*.tgz" -Recurse | Select-Object -First 1
                if (-not $unbrandedTgz) {
                    throw "Could not find unbranded emitter .tgz in build artifacts at: $BuildArtifactsPath"
                }
                Write-Host "Using unbranded package from build artifacts: $($unbrandedTgz.FullName)"