Repository navigation
Give each release its own build-numbered tag - #6
Merged
Merged
Conversation
Releases are tagged with the MarkText tag plus a build number (v0.20.0.1, v0.20.0.2, ...), one higher than the highest existing tag for that MarkText version, so a rebuild with a newer NativeBoat no longer replaces an earlier release. The ZIP is named after the release tag.
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
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.
A release run used to reuse the MarkText tag (e.g.
v0.20.0) as its release tag, so rebuilding the same MarkText version, for example with a newer NativeBoat, replaced the earlier release and its files.<marktext-ref>.<n>.nis one higher than the highest existing numbered tag for that MarkText version, so the first build ofv0.20.0isv0.20.0.1. Existing tags are read from the repo's git refs, so a number is never reused, and.10sorts above.9. The ZIP is renamed to match (MarkText-v0.20.0.1-native-win-x64.zip) andSHA256SUMS.txtis regenerated. The step that edited existing releases is removed;gh release createfails rather than overwrites if the tag already exists.The existing
v0.20.0release is left untouched.The tag numbering and ZIP renaming were checked locally against simulated tag lists. The workflow itself hasn't been run yet.