Skip to content
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

Open
jrief-digikey opened this issue Nov 10, 2022 · 7 comments
Open

Swift package manager tag naming convention #115

jrief-digikey opened this issue Nov 10, 2022 · 7 comments

Comments

@jrief-digikey
Copy link

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?

@viaskal-sift
Copy link
Contributor

Thanks @jrief-digikey for bringing this, we'll take a look

@SujishaExalture
Copy link
Contributor

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

@jrief-digikey
Copy link
Author

@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".

@SujishaExalture
Copy link
Contributor

Thanks for the catch. @jrief-digikey . We will consider for sure

@jordanhbuiltbyhq
Copy link

I had to select the master branch because of this issue, up to next major version doesn't work.

@andrewjmeier
Copy link

Hey @SujishaExalture can we get an update on this?

@viaskal-sift
Copy link
Contributor

@jrief-digikey seems, nowadays this version pattern is already supported by Swift, could you pls confirm the issue is not relevant anymore

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants