use version scriptlet instead of hardcoded version #1164
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
Signed-off-by: Ondrej Kubik <ondrej.kubik@canonical.com>
<
590C
div data-view-component="true" class="flash flash-warn mt-3">
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.
moving to use version script instead of hardcoded version which needs to be updated every release
With this in place, we might abandon build from wekan-snap repository and instead just promote to stable channel builds based on tagged version.
Version should represent last tag + number of git commit since + last git commit id (e.g. 0.32-10-g57219df)
in case of build from tag, this will end up being only tagged version (e.g. 0.32) so we can clearly distinguish those in store when promoting.
Also when bugs are reported, we have easy way to track version they are on in case of non stable channel
This change is