Pre-Release Versioning Support #293

Closed
dlvenable opened this Issue May 31, 2012 · 10 comments

Comments

Projects
None yet
5 participants
Contributor

dlvenable commented May 31, 2012

Semver section 10 provides a standard for pre-release versions. When I created a podspec and ran 'pod spec lint' against it, the following error occurred:

Malformed version number string 1.0.0-beta.1

I am using 0.5.1 installed as a gem.

Owner

alloy commented May 31, 2012

Indeed. Unfortunately RubyGems (of which we use the Version class) does it a little differently. In your case it should be 1.0.0.beta1.

For now there isn't much that we can do about that, nor do I know if that's something we want to support in the future. (I’d rather just re-use the RubyGems Version class as-is).

@alloy alloy closed this May 31, 2012

Contributor

dlvenable commented May 31, 2012

Thanks - that is very helpful to know. The CocoaPods wiki references semver, but does not mention Ruby versioning. Perhaps the wiki should be update to reflect the correct version numbers. Is there a URL the wiki could link to which provides the correct version rules for RubyGems?

This is the wiki page I'm referring to:
https://github.com/CocoaPods/CocoaPods/wiki/Dependency-version-workflow

Owner

alloy commented May 31, 2012

Not that I know of right now. Unfortunately I don't have the time right now to find that and update the wiki... Would you mind updating that wiki page with this specific instruction?

Contributor

dlvenable commented May 31, 2012

Yes, I can update it.

Owner

alloy commented May 31, 2012

Thanks!

Contributor

lukeredpath commented Jun 1, 2012

Might it be worth opening an issue on the RubyGems project?

Owner

alloy commented Jun 3, 2012

@lukeredpath That’s probably a good idea. It would probably take a while before it would be available for us to use, though. Especially as we try to support the RubyGems version that comes with 10.7. If they release it fast enough for it to be included in 10.8, then it would definitely be something we could use.

Contributor

Ashton-W commented Jan 8, 2013

This is still an issue. I am trying to get a library on board with CocoaPods, they already use Semver but RubyGems Version doesn't support their pre-release tags - and so neither does CocoaPods.
I understand encouraging developers to use Semver - but requiring them to support RubyGems Version quirks, seems wronng for Objective-C libraries.
We should only ask they follow canonical Semver, and not spread RubyGems quirks.

Owner

alloy commented Jan 10, 2013

@Ashton-W Yeah you’re right. In the upcoming version we completely vendor the source from RubyGems that we need, so it will be much easier for us to fix this locally anyways.

/cc @irrationalfab

@alloy alloy reopened this Jan 10, 2013

Owner

fabiopelosin commented Feb 25, 2013

This issue should have been solved in CP 0.17

jzapater pushed a commit to jzapater/CocoaPods that referenced this issue Sep 17, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment