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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
makefile: add command to generate git release tags #720
makefile: add command to generate git release tags #720
Changes from all commits
89a2377
3da789e
183b11a
5d1fd00
6114235
c82d079
ee0b36a
4d6aa3a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bit confused on this switch, do we ever want appStatus without preRelease? From the tapd tags it looks like we only do both or neither, ex.
v0.3.2
,v0.3.0-alpha.rc3
, but nov0.3.0-alpha
norv0.3.0-rc3
.Or is this to also match a different pattern used for a different project?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should make sure that possibility is available to us. I don't think we have a strict org wide rule around the use of status without pre-release. For instance,
v0.3.0-alpha
seems like a reasonable tag to me.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
K, I thought leaving out the
rc1
suffix when usingalpha
orbeta
is what caused issues previously? I don't recall exactly which tag caused those though.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What caused the issue previously was leaving out
-alpha
while just using anrc
tag (e.g.0.3.2-rc2
), because then the version check of the release script didn't work as it just did a substring comparison with what the app version string reported (v0.3.2-alpha.rc2
).So I think we should also update the
check_tag_correct
function inscripts/release.sh
to use the newget-git-tag-name.sh
script and compare it to the checked out tag.And to answer your other question, just having the status is what we want for non-RC releases in all other projects than this one (e.g. lnd).