Pod::Spec.new do |s|
  s.name         = "SCPullRefresh"
  s.version      = "0.1"
  s.summary      = "A pull refresh for easily customize refresh animation"
  s.homepage     = "https://github.com/singro/SCPullRefresh"
  s.license      = { :type => 'MIT', :file => 'LICENSE' }
  s.author       = "singro"
  s.source       = { :git => "https://github.com/singro/SCPullRefresh.git", :tag => s.version.to_s }
  s.source_files = 'SCPullRefresh'
  s.requires_arc = true

  s.platform = :ios, '7.0'
  s.ios.deployment_target = '7.0'
  s.frameworks = 'Foundation', 'UIKit'
end
Pod::Spec.new do |s|
  s.name         = "SCPullRefresh"
  s.version      = "0.0.1"
  s.summary      = "A pull refresh for easily customize refresh animation"
  s.homepage     = "https://github.com/singro/SCPullRefresh"
  s.license      = { :type => 'MIT', :file => 'LICENSE' }
  s.author       = "singro"
  s.source       = { :git => "https://github.com/singro/SCPullRefresh.git", :tag => s.version.to_s }
  s.source_files = 'SCPullRefresh'
  s.requires_arc = true

  s.platform = :ios, '7.0'
  s.ios.deployment_target = '7.0'
  s.frameworks = 'Foundation', 'UIKit'
end
Fix pod spec source tag
Fix pod spec source tag

There are other methods of specifying the location of source code
instead of tags, but you should really be using tags to mark your code
commit for your spec. If you are not the owner of the repository you
are creating a spec for, file an issue with the repository to request
that a tag be made. If this doesn’t work, then you should specify the
version of your podspec to begin at 0.0.1 to indicate that this pod’s
spec is unmanaged. Should the owner finally get a tag, then you can
update the podspec with the correct version with little fear of
conflicting with your previously unmanaged podspec’s version.
