Draft
Conversation
Collaborator
|
The relevant issue for this is #938 and the design needs to be worked out there (and how to handle if this is a breaking change) before moving on to a PR. |
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.
I am using cargo-edit to add metadata tags to my version string. For the moment, I am having trouble with adding metadata to version with pre-release tags (ex. 0.1.0-dev).
cargo set-version -m metawill remove the pre-release and replace it with the meta tag (0.1.0+meta).This MR will fix this behaviour to respect the dev tag, so the correct version will be 0.1.0-dev+meta.
Let me know what you think! (and thanks for making cargo-edit!)