Repository navigation
Publish releases to NuGet with Trusted Publishing - #45
Merged
Merged
Conversation
A published GitHub release packs FormHelper and FormHelper.FluentValidation, pushes them to nuget.org with a short-lived key from Trusted Publishing (no stored API key) and attaches the scripts, styles and packages to the release. Stops when the release tag doesn't match the version in Directory.Build.props. Replaces release-assets.yml.
It issues the NuGet key; a tag could be moved.
|
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
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.
When a GitHub release is published,
release.ymldoes the following. It never runs on a push.<Version>insrc/Directory.Build.props, and stops otherwise.It replaces
release-assets.yml. The Trusted Publishing policy on nuget.org points at this workflow file.