SwiftPM Package Resolution Failed for v3.3

[colemcampbell]

Swift Package Manager doesn't seem to be picking up the newest version of Gifu, causing package resolution to fail if you try to update to v3.3.

because no versions of Gifu match the requirement 3.3.0..<4.0.0 and root depends on Gifu 3.3.0..<4.0.0, version solving failed.

[colemcampbell]

The reason seems to be that SwiftPM expects a three period separated integer for the version number like 3.3.0, but the version tag is 3.3.

From Apple Developer:

Tag Your Latest Commit

It’s a best practice to create a version tag for a Swift package; however, there are other ways to add a package to a project, as described in Adding Package Dependencies to Your App. To create a version tag, tag the last commit with the package version. A package version is a three period-separated integer. An example is 1.0.0. The package version must conform to semantic versioning to ensure that your package behaves in a predictable manner when developers update their package dependency to a newer version.

[rval]

Running into the same thing. I was able to use SPM to install the v3.3 branch, but it doesn't work with the tag.

[kaishin]

Fixed. Thanks @kean for the reminder!

[ManuEspeso]

@kaishin This changed breaks cocoapods installation, I've tried all possibilities (pod install, pod repo update, pod update ...) in a project with Gifu 3.3 and fails because cocoapods doesn't find any version with this tag

[kaishin]

I will push a fix momentarily.

[kaishin]

I restored the v3.3 tag for now. Sorry for the inconvenience.

[ManuEspeso]

Thanks for the quick response!