Updating github workflow file to use nuget-acceptable version numbers for packaging #517
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.
Fixes 513 and should unblock builds.
This change alters the versioning used by github actions for builds by utilizing the Github Run Identifier as an "Additional Label" (in semver parlance) rather than a major version number.
Example (from this failed build)
2564178360
(System.ArgumentException: PackageVersion string specified '2564178360' is invalid.
)6.0.0-build.2564178360
This matches the semver logic:
Example: 1.0.0-alpha < 1.0.0-alpha.1 < 1.0.0-alpha.beta < 1.0.0-beta < 1.0.0-beta.2 < 1.0.0-beta.11 < 1.0.0-rc.1 < 1.0.0.
(ref: https://semver.org/)