Ideally you will want to add a tag to your repository and change the podfile from :commit => '...' to :tag => 'tag'.
Added podspec file
Updated commit on Podspec
Thanks for adding this! I can't pull it in yet because it doesn't quite work: we need a way to mark StoreKit as optional to the compiler (see step three of Getting Started in the readme). Is there a way to do that in the podspec?
Using StoreKit as weak
Sure, what do you think about it now?
Can you fill me in on how tagging interacts with CocoaPods? If we use tags will we have to update the tag and the podspec file every time we change something? Is there any way to just have it grab the most recent commit to master?
That would be the idea. That way if there any compatibility issue it would break any app, works pretty much like a ruby gem. If the user wants, he can always override that in his app.
Basically you tag each release, you can start with 0.0.1. Between releases if a user want to get e bleeding edge version he can add pod 'Appirater', :git => 'repository' and get the latest commit.
pod 'Appirater', :git => 'repository'
@nathangreenstein let me know if you have any questions on CocoaPods
Merging this in now. @gabrielrinaldi can you keep an eye on the podspec file, and send pull requests whenever you think it needs updating? The change to the repo are usually very small (localization additions/modifications) so it probably only needs updating after several commits.
@arashpayan sure, can you create a tag so I can submit the Podefile? Podfiles will not pass validation if it don't have a tag. For the one included now in your repository you can keep updating the commit hash to the last available. The one we submit to the Spec repository needs a tag.
@gabrielrinaldi if I give you commit privilieges would you mind doing the tagging now and in the future? :-) I can easily see this being something that I'll forget/neglect to do.
Cool. I added you as a collaborator. Thanks!