Add automated NuGet publishing workflow#37
Merged
RevenantX merged 1 commit intoRevenantX:masterfrom Mar 18, 2026
Merged
Conversation
Contributor
Author
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
2 participants
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
This PR adds a GitHub Actions workflow that automatically publishes to NuGet.org when the version in the csproj changes.
How it works:
<Version>in LiteEntitySystem.csproj against the latest version on NuGet.orgSetup required:
You'll need to add a
NUGET_API_KEYsecret to your repository settings with your NuGet.org API key.Why this is useful:
Version 1.2.0 was released on GitHub back in February but NuGet still only has 1.0.1. This workflow ensures NuGet stays in sync with GitHub releases automatically.
Workflow adapted from Anointed Automation's open source C# libraries which use the same pattern successfully.