fix(release): keep latest release tag and metadata current - #1136
Merged
Conversation
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
1 participant
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.
Root cause: ncipollo release-action with allowUpdates/replacesArtifacts updated the ancient latest release's assets but did not move its existing lightweight latest tag. The live release was created/published 2024-03-10, while latest pointed at 29b592d and its new manifest identified 7f82b9e. This adds release metadata from the manifest to the body and explicitly retargets/verifies refs/tags/latest to the current main SHA after asset update. The mutable latest release will be recreated after merge to refresh its presentation date while preserving its assets; historical dated releases remain untouched.