Repository navigation
feat: Automated NuGet publishing on release tags - #1
Merged
Merged
Conversation
- Trigger on version tags (v*.*.*) - Run tests across .NET 6/7/8 before publishing - Extract version from tag and apply to packages - Publish both MeshGuard and MeshGuard.SemanticKernel Required secret: NUGET_API_KEY
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.
Summary
Adds automated publishing to NuGet when version tags are pushed.
Workflow
v*.*.*MeshGuardandMeshGuard.SemanticKernelpackagesRequired Secrets
Configure this secret in the repository settings:
NUGET_API_KEYCreating the NuGet API Key
MeshGuardMeshGuard.SemanticKernelUsage
To publish a new version:
The version is automatically extracted from the tag and applied to packages.
Closes
Issue #7