Release a tagged version? about kif HOT 9 CLOSED

That's a +1 on that. @CocoaPods does not accept new versions (at least ones that are not created by project developers) that are not based on a tag. Adding tags would make it super easy to create cocoapods versions. Especially since the latest KIF pod is quite outdated (over 5 months).

from kif.

Any suggestions on a commonly used tagging format?

On Tue, Sep 25, 2012 at 6:47 AM, Pawel Dudek [email protected]:

That's a +1 on that. @CocoaPods https://github.com/CocoaPods does not
accept new versions (at least ones that are not created by project
developers) that are not based on a tag. Adding tags would make it super
easy to create cocoapods versions. Especially since the latest KIF pod is
quite outdated (over 5 months).

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/146#issuecomment-8854718.

from kif.

Cocoapods recommend using semver for tags (aka versioning through tags in git). You can read more here. Just scroll down through the enormously long list till you reach readme.

from kif.

Specifically, a tag of anything greater than 0.0.1, since untagged repos get 0.0.1 as an initial version in Cocoapods.

@efirestone, if you could tag and push, I can push an updated Podspec.

from kif.

As a concrete example, Urban Airship has quite a few tags, see: https://github.com/urbanairship/ios-library/tags.

from kif.

+1 on this - I've just discovered it after filing #164.

from kif.

+1. Tags would be swell.

from kif.

+1

from kif.

Done as part of #231. Podspec pull request here: CocoaPods/Specs#3973

from kif.