Default "Up to major version" dependency rule in Xcode incompatible with Pow's 0.X versioning
warpling opened this issue · comments
Ryan McLeod commented
Joe Fabisevich commented
Hey @warpling, it seems like this problem is on Xcode’s side. Semantically there's nothing wrong with versioning a library in the 0.x.x range, the number is generally reserved for pre-release versions. I can understand from Xcode's side why they choose to assume that libraries are 1.0.0 and higher, but it still seems like they should handle pre-release libraries more gracefully.
The good news is that we just released version 1.0.0, so this won't be a problem going forward regardless and I feel safe closing this issue out. 🙂