ci(publish): add a nuget.org publish lane gated on NUGET_API_KEY - #84
Merged
Conversation
Downstream stable SDKs cannot ship to nuget.org while Geospatial.Grpc is only on the authenticated GitHub Packages feed (honua-sdk-dotnet#264). Push to nuget.org after the GitHub Packages push whenever the NUGET_API_KEY secret is configured; skip with a warning when it is not.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Downstream stable SDKs cannot publish restorable packages to nuget.org while
Geospatial.Grpclives only on the authenticated GitHub Packages feed — the blocker tracked as honua-sdk-dotnet#264.Adds a
Publish to nuget.orgstep after the GitHub Packages push: when theNUGET_API_KEYsecret is configured it pushes the same artifacts to nuget.org with--skip-duplicate; when absent it skips with a::warning::instead of failing, so the existing GitHub Packages release path is unchanged until the credential exists. These packages are unsigned, which nuget.org accepts (it repository-signs all uploads).Once the secret is in place, dispatching this workflow on tags
v0.1.0-alpha.2(the version honua-sdk-dotnet pins) andv0.1.0-alpha.3puts both on the public feed.