NotificationsYou must be signed in to change notification settings
Fork100
Star551

[WIP] Experiment on getting GitHub Packages packages correct casing#1855

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Draft

o-l-a-v wants to merge4 commits intoPowerShell:master

base:master

Choose a base branch

fromo-l-a-v:fix-1446-github-packages-lowercase

Draft

[WIP] Experiment on getting GitHub Packages packages correct casing#1855

o-l-a-v wants to merge4 commits intoPowerShell:masterfromo-l-a-v:fix-1446-github-packages-lowercase

Conversation

Copy link

Contributor

o-l-a-v commentedAug 11, 2025•
edited
Loading

PR Summary

Just experimenting on getting correct casing of GitHub Packages packages.

Far from done, just an idea on how one could get correct casing on GitHub Packages NuGet v3 packages.

It builds, and I've tested it against NuGet organization packageNuGet.Internal.GithubIssueTagger:

PS>Save-PSResource-TrustRepository-Path ([System.Environment]::GetFolderPath('Desktop'))-Verbose-Repository'gh-nuget'-Name'NuGet.Internal.GithubIssueTagger'VERBOSE: Setting Secret Management network credentialsVERBOSE: credential successfully readfrom vault and setfor repository: gh-nugetVERBOSE: Attempting to searchfor packagesin'gh-nuget'VERBOSE: Performing the operation"Save-PSResource" on target"Package to save: 'nuget.internal.githubissuetagger', version: '2025.4.30'".VERBOSE: Performing the operation"Save-PSResource" on target"Package to install: 'nuget.internal.githubissuetagger', version: '2025.4.30'".VERBOSE: This resource is not a PowerShell package and will be installed to the modules path: .VERBOSE: pkgName:"nuget.internal.githubissuetagger", actual name of nuspec file:"NuGet.Internal.GithubIssueTagger.nuspec"VERBOSE: Installation source path is:'C:\Users\<redacted>\AppData\Local\Temp\fb55f6b9-3acb-445c-8b5b-3e14e3e57537\nuget.internal.githubissuetagger\2025.4.30'VERBOSE: Installation destination path is:'C:\Users\<redacted>\Desktop\nuget.internal.githubissuetagger\2025.4.30'VERBOSE: Attempting to move'C:\Users\<redacted>\AppData\Local\Temp\fb55f6b9-3acb-445c-8b5b-3e14e3e57537\nuget.internal.githubissuetagger\2025.4.30' to'C:\Users\<redacted>\Desktop\nuget.internal.githubissuetagger\2025.4.30'VERBOSE: Successfully installed package'nuget.internal.githubissuetagger' to location'C:\Users\<redacted>\Desktop'VERBOSE: Attempting to delete'C:\Users\<redacted>\AppData\Local\Temp\fb55f6b9-3acb-445c-8b5b-3e14e3e57537'VERBOSE: Successfully deleted'C:\Users\<redacted>\AppData\Local\Temp\fb55f6b9-3acb-445c-8b5b-3e14e3e57537'PS>

See verbose line about pckName vs actual name of nuspec file.

The API returns package ID as lowercase (see#1446 (comment)), so the idea is to extract the.nupkg and get info from its' content.

So, we can work around / mitigate / fix the casing of the install path this way, but the output fromFind-PSResource will be lowercase, because that's what the API returns.

PR Context

PR Checklist

PR has a meaningful title
- Use the present tense and imperative mood when describing your changes
Summarized changes
Make sure all.h,.cpp,.cs,.ps1 and.psm1 files have the correct copyright header
This PR is ready to merge and is notWork in Progress.
- If the PR is work in progress, please add the prefixWIP: or[ WIP ] to the beginning of the title (theWIP bot will keep its status check atPending while the prefix is present) and remove the prefix when the PR is ready.
Breaking changes
- None
- OR
- Documentation needed
  - Issue filed:
User-facing changes
- Not Applicable
- OR
- Documentation needed
  - Issue filed:
Testing - New and feature
- N/A or can only be tested interactively
- OR
- Make sure you've added a new test if existing tests do not effectively test the code changed
Tooling
- I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
- OR
- I have considered the user experience from a tooling perspective and enumerated concerns in the summary.