You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was glad to see support for Swift Package Manager landed recently (#119).
Unfortunately, a commit hasn't been tagged since that PR was merged, so Swift Package Manager users need to point to a commit or a branch, rather than simply defining a version requirement.
The version requirements, which follow Semantic Versioning (SemVer) conventions, are used to determine which Git tag to check out and use to build the dependency.
Could a new patch version be tagged for the sake of more convenient usage with Swift Package Manager?
The text was updated successfully, but these errors were encountered:
I was glad to see support for Swift Package Manager landed recently (#119).
Unfortunately, a commit hasn't been tagged since that PR was merged, so Swift Package Manager users need to point to a commit or a branch, rather than simply defining a version requirement.
From https://swift.org/package-manager/
Could a new patch version be tagged for the sake of more convenient usage with Swift Package Manager?
The text was updated successfully, but these errors were encountered: