Drop 'v' prefix from tag names #9
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
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.
Links
Closes #7
Background
While it was a bug in the Swift Plagrounds app and its a common standard, using the
vprefix for tags is unnecessary but I just followed the pattern from some other repos originally 😄After having a look at other repos, I now realise that the norm is to just have plain semantic versions for tag names (such as
0.0.3instead ofv0.0.3).Description
In this PR, I just drop the
vprefix from the Podspec, and going forward we can just tag the next release as0.0.3rather thanv0.0.3.