Merged
Conversation
Owner
|
You are right, do you have ideas on how to update automatically the version ? |
Contributor
Author
|
I did some searching and it seems to be a common problem. I didn't find any solutions either. Most people have some manual process where they just have to remember to bump the version before they create the release. I can also just override the version in my ebuilds so it's not the end of the world if it doesn't get updated. Thanks for merging this! |
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
2 participants
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.
The build number in Cargo.toml still says 0.18.1 and should probably be updated to match the actual latest release.
(Also it creates extra work for me to patch the version in my ebuilds for gentoo)