Summary
The publish workflow's stamp step queries the GitHub releases/latest API to get the version for the "Latest · vX.Y.Z" display name. On a tag push, the Release object may not exist yet, causing the stamp to show the previous release version.
Observed in run 26770200319: v0.14.0 publish stamped "Latest · v0.13.0".
Fix
Use the already-resolved tag from the earlier resolve step instead of the API call. The tag is always correct since it comes from the trigger event itself.
nvsentinel and topograph already use this pattern.
Summary
The publish workflow's stamp step queries the GitHub
releases/latestAPI to get the version for the "Latest · vX.Y.Z" display name. On a tag push, the Release object may not exist yet, causing the stamp to show the previous release version.Observed in run 26770200319: v0.14.0 publish stamped "Latest · v0.13.0".
Fix
Use the already-resolved tag from the earlier
resolvestep instead of the API call. The tag is always correct since it comes from the trigger event itself.nvsentinel and topograph already use this pattern.