The 0.17.0 release was first tagged v0.17.0. MinVer has no MinVerTagPrefix configured, so it ignored the tag and computed 0.16.5-alpha.0.31 from the previous 0.16.4 tag. That prerelease had already been pushed by the preview workflow, so every dotnet nuget push reported "already exists", which --skip-duplicate swallowed. The Publish NuGet run went green without publishing anything (https://github.com/Eventuous/eventuous/actions/runs/35508816930).
Options (not mutually exclusive):
- Set
<MinVerTagPrefix>v</MinVerTagPrefix>, or otherwise accept both 0.x.y and v0.x.y tags. The current convention is bare tags, so this would need to be decided explicitly.
- Add a guard step in
publish.yml that fails when the tag isn't a valid SemVer version, or when the packed package version doesn't equal the tag name.
- Restrict the workflow's
tags filter to a version pattern (e.g. '[0-9]+.[0-9]+.[0-9]+*') so stray tags don't trigger a publish run at all.
The 0.17.0 release was first tagged
v0.17.0. MinVer has noMinVerTagPrefixconfigured, so it ignored the tag and computed0.16.5-alpha.0.31from the previous0.16.4tag. That prerelease had already been pushed by the preview workflow, so everydotnet nuget pushreported "already exists", which--skip-duplicateswallowed. The Publish NuGet run went green without publishing anything (https://github.com/Eventuous/eventuous/actions/runs/35508816930).Options (not mutually exclusive):
<MinVerTagPrefix>v</MinVerTagPrefix>, or otherwise accept both0.x.yandv0.x.ytags. The current convention is bare tags, so this would need to be decided explicitly.publish.ymlthat fails when the tag isn't a valid SemVer version, or when the packed package version doesn't equal the tag name.tagsfilter to a version pattern (e.g.'[0-9]+.[0-9]+.[0-9]+*') so stray tags don't trigger a publish run at all.