Pod’s page should be pinned its latest stable release version

[friedbunny]

When testing out whether or not to publish pre-release builds to CocoaPods (mapbox/mapbox-gl-native#6235), I noticed that cocoapods.org immediately switched to showing the new, pre-release version — 3.4.0-alpha.3, in this case.

CocoaPods (the tool) doesn’t upgrade developers to pre-release pods unless they explicitly specify such a version and I expected the website to continue showing the latest stable release version, too.

We at Mapbox don’t want the average developer to use pre-releases. We’d like to be able to publish pre-release versions to CocoaPods for testers, but this is currently blocking us from doing that.

I’ve since deleted the 3.4.0-alpha.3 from CocoaPods trunk and the page is back to the latest stable release.

[orta]

We do this ( http://blog.cocoapods.org/Release-Versions-Only/ ) - I think that CocoaPods is not considering your version a SemVer pre-release version, which should be improved in the next CP release - CocoaPods/Core#350

[codytwinton]

@friedbunny @orta - I'm not sure if this is a regression, but I'm running into a similar issue with the latest version of the website.

[friedbunny]

@codytwinton As far as I’m aware, this was never fixed. Mapbox does currently push pre-releases to trunk, as we eventually decided that being able specify pre-releases in podfiles was more important than the CocoaPods website being a bit reckless with versioning. 😉

[codytwinton]

well. damn. rip.