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
Could you consider pushing 2.4.2 to the trunk as an exception?
I'd like to use BrickKit as a dependency in a podspec I am creating, but am currently limited to using 2.4.0 which is not Swift 4.0 compatible. Since podspecs don't currently support a mix of Swift 3.2/4.0 (CocoaPods/CocoaPods#7134) the podspec can only use Swift 3.2 pod dependencies if BrickKit is included.
While a Podfile can specify a pod that is not yet pushed to the trunk (using :git and :tag), a podspec cannot do the same with a dependency.
Thanks for considering this request.
The text was updated successfully, but these errors were encountered:
It appears that only minor versions are being pushed to CocoaPods/Specs
https://github.com/CocoaPods/Specs/search?q=BrickKit&type=Commits
Could you consider pushing 2.4.2 to the trunk as an exception?
I'd like to use BrickKit as a dependency in a podspec I am creating, but am currently limited to using 2.4.0 which is not Swift 4.0 compatible. Since podspecs don't currently support a mix of Swift 3.2/4.0 (CocoaPods/CocoaPods#7134) the podspec can only use Swift 3.2 pod dependencies if BrickKit is included.
While a Podfile can specify a pod that is not yet pushed to the trunk (using :git and :tag), a podspec cannot do the same with a dependency.
Thanks for considering this request.
The text was updated successfully, but these errors were encountered: