Update podspec version to 7.3.0

[artemsmikh]

Hi, I guess the version in the .podspec file also need to be updated in order to push the changes to CocoaPods. I am asking anyone with the right permission to also add a tag 7.3.0 and push the new podspec to the CocoaPods trunk via pod trunk push GBDeviceInfo.podspec. Thanks!

[cpsauer]

Hey, Artem! Have been discussing CocoaPods with Luka--and don't have permissions just yet. (Holding off on merge only so we're tracking that it hasn't been done; looks great to me; thanks for contributing.)

In the meantime, is there a good way to consume the latest commit directly from CocoaPods? (I'm actually using the code via a different mechanism.) I'm trying to think about ways we could automate or eliminate this step, since the latest commit is basically always what people want.

[artemsmikh]

Hi @cpsauer, thanks! Yes, there is a way to do what you've said. You can specify a link to the repo directly in the Podfile like this:

pod 'GBDeviceInfo', :git => 'https://github.com/lmirosevic/GBDeviceInfo.git'

I'm using it like this now, since the version in the CocoaPods is outdated and doesn't have information about the newest iPhones. However, I'm not sure this is a good way to always use it like this, it's more like a hack until the repo owner pushes a new version to CocoaPods. You're right, many users would like to have the pod containing all the latest changes as soon as possible, but on the other hand, another thing that users expect is a certain level stability, and consistently relying on the latest commit sidesteps the stability and predictability that versioned releases provide.

[cpsauer]

(#152 is about the same. A little more discussion over there, but let's centralize here.)

Perhaps there's also a good way to do it per-commit and still keep reproducibility, either with cocoapods or with SPM? I'm not sure just how much SPM has taken over from pods, but while we're discussing this--and waiting for a call&permissions--I thought it might be worth discussing what primary distribution mechanism would be best in case it's changed.

(As in #152 (comment) IMO "living at head" can have some strong benefits, if (and only if) there's a natural way to consume libraries that way from Xcode. That is having the main branch represent the latest-and-greatest state, and people grabbing the latest by commit (reproducible) or branch (if it's a fast-and-loose kinda thing where they want auto updates). Benefit is that it equips everyone to go direct and easily hack on the project and contribute and keep things easily community maintained. But if it doesn't work smoothly from Xcode then we obviously shouldn't do that. Would love your all's opinion on what's best overall!)