feat: NuGet release/test workflows #3
Merged
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.
This PR introduces three workflows:
Functionally the dev and proper releases are the same (and dispatched by hand). They will might differ a bit in the future especially in terms of how the package tag is derived.
Currently both releases grabs the first version from the CHANGELOG.md and use that for the package's name. For dev releases you would manually add a version to the start of the CHANGELOG.md such as 0.0.3-dev.1.
Future work will include grabbing the changelog entry for the latest version and applying it to the PackageReleaseNotes tag in the package's .csproj
Minor code changes: