Renaming published packages after product rename #236595
-
|
We've been publishing new versions of Dev Proxy, Microsoft.DevProxy and Microsoft.DevProxy.Beta. The project has recently been onboarded to the .NET Foundation, as part of that process we have moved from the Microsoft org on GitHub to the dotnet org, and therefore we would like to start publishing using DotNet.DevProxy and DotNet.DevProxy.Beta names. Is there any guidance on what we should do with the packages that we have already published under Microsoft.DevProxy? Can we bulk update them? /cc @mdanish-kh |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Changing the PackageId would be a breaking move, in the sense that any person or script relying on If the Registry / ARP publisher value is also changed in the new versions, then there is guidance in our FAQ to somewhat gracefully handle the publisher change. Basically, you would retain but pause publishing under the old PackageId ( If the Registry / ARP metadata is the same, the cleanest way is to just open PRs to "move" all the versions from the old PackageId to the new one. The "move" is done in two steps, one PR to remove the version from older ID & another to add it in a new one. To make this easy, the community developed some tooling to help with the move operation. If you run YamlCreate.ps1, you'll see an option to "Move package to a new identifier", it'll help you automatically create all these PRs Open to see screenshot
FWIW the packages under the dotnet GitHub org are published under the package ID |
Beta Was this translation helpful? Give feedback.
Changing the PackageId would be a breaking move, in the sense that any person or script relying on
winget install Microsoft.DevProxyto install the package would fail. A more thorough solution depends on microsoft/winget-cli#1900 & microsoft/winget-cli#1899. If still required, a question would be if this org change is also accompanied by a change in the installer where it writes a differentPublishervalue to Registry?If the Registry / ARP publisher value is also changed in the new versions, then there is guidance in our FAQ to somewhat gracefully handle the publisher change. Basically, you would retain but pause publishing under the old PackageId (
Microsoft.DevProxy) & publish new versi…