-
Notifications
You must be signed in to change notification settings - Fork 26
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
Swift package manager tag naming convention #115
Comments
Thanks @jrief-digikey for bringing this, we'll take a look |
We cannot add additional tags. The version rule requires Swift packages to conform to semantic versioning . The Xcode Swift package manager should be tags of the form X.X.X (i.e. 2.1.1). A package version is a three period-separated integer, for example 1.0.0. It must conform to the semantic versioning standard in order to ensure that your package behaves in a predictable manner once developers update their package dependency to a newer version. To learn more about the semantic versioning standard, visit https://semver.org |
@SujishaExalture Agreed, Xcode is requiring tags following the semver standards, however Sift is preceding tags with a "v". I'm recommending that Sift drop the preceding "v". |
Thanks for the catch. @jrief-digikey . We will consider for sure |
I had to select the master branch because of this issue, up to next major version doesn't work. |
Hey @SujishaExalture can we get an update on this? |
@jrief-digikey seems, nowadays this version pattern is already supported by Swift, could you pls confirm the issue is not relevant anymore |
The Xcode Swift package manager seems to prefer tags of the form X.X.X (i.e. 2.1.1). Can an additional tag be added to the release to support Xcode?
The text was updated successfully, but these errors were encountered: