Skip to content
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

Using git hash in released versions #19

Open
rgildein opened this issue Nov 25, 2024 · 1 comment
Open

Using git hash in released versions #19

rgildein opened this issue Nov 25, 2024 · 1 comment

Comments

@rgildein
Copy link

Currently, we are craftctl set version="${TAG#v}" to set snap version. With this approach, there is no way to distinguish between release version in snapstore.
Example (screenshot) below show 3 different release in each channel, but version is same for all of them.
Screenshot from 2024-11-25 21-08-17

I believe that we should use something like <tag>-<commit-hash> for any commits ahead of tag, and <tag> only for commits marked with tag.

Copy link

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/SOLENG-900.

This message was autogenerated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant