Repository navigation
Publish NuGet packages to nuget.org (trusted publishing) + release 1.0.5 - #2
Merged
Merged
Conversation
v* tags now push the embeddable packages to nuget.org as well as GitHub Packages. Authentication uses nuget.org trusted publishing (GitHub OIDC via NuGet/login), so no API key is stored in the repository.
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.
What
v*tags now publish the eight embeddable packages to nuget.org, as well as GitHub Packages. Before this, they were only on GitHub Packages, which requires a token even to install public packages.NuGet/login@v1, withuser: rvegajr. No API key is stored anywhere. Only thepublish-nugetjob getsid-token: write.chore(release): 1.0.5bumpsDirectory.Build.propsandjs/package.json, the same way 1.0.3 and 1.0.4 were released.Package contents
Unchanged from 1.0.4: this PR touches no source under
src/. Pushes use--skip-duplicate, so re-running a release is safe.Before tagging
v1.0.5This requires a nuget.org trusted publishing policy:
rvegajrYOLOVibeCode/ez-odata-apici.ymlEzOdata.Core,EzOdata.Connectors.*,EzOdata.OData,EzOdata.Rest,EzOdata.Docs,EzOdata.Embedded,EzOdata.AspNetCore,EzOdata.WebApiAs with every
v*tag, the release also publishes npm1.0.5.