Packager succeeded but did not create a package

[KyrosKrane]

Packager succeeded but did not create a package

[nebularg]

Are you using annotated tags?

[KyrosKrane]

Are you using annotated tags?

I'm not sure what that is. When I create a new tag, I do put the same value in the tag name and tag message, if that's what you mean. Example:

[KyrosKrane]

I just looked up the details. It's indeed an annotated tag, as I put a message and sign the tag. Confirmed on the git command line as well.

[nebularg]

Yea, I really have no idea why it didn't use the release tag. It should have, the log shows that it was there. The docs say it should have been used.

I can't reproduce it, so I'm going to just blame github since the packager did what it was suppose to with the output it got from git.

[Nevcairiel]

I assume this is from having two tags on the same commit, and git describe to generate the version was still using the original alpha tag, because why would it have any preference to take one over the other if both are at the same point in history?

Which one it chooses might just be random, and you got lucky in the past.

[nebularg]

nah, it looks at date if there are multiple matches. that's why i asked about annotated tags, lw tags don't have their own object with a date, so git will just (randomly) use whatever is in ref list first

For each commit-ish supplied, git describe will first look for a tag which tags exactly that commit. Annotated tags will always be preferred over lightweight tags, and tags with newer dates will always be preferred over tags with older dates.

[nebularg]

Hopefully fixed with a8acbfa