Pre-release Versions Do Not Conform to Semantic Versioning Spec #4

Closed
blakewatters opened this Issue Feb 10, 2013 · 1 comment

Comments

Projects
None yet
1 participant
Contributor

blakewatters commented Feb 10, 2013

This is a migration of the issue tracked on CocoaPods/CocoaPods#583 and the associated Pull Request CocoaPods/CocoaPods#584 into the Core module.

I just pushed a version of the RestKit Podspec with the version 0.20-dev. On testing the installation, version.rb blew up at me complaining that the version string is malformed. I checked the Podspec format document @ https://github.com/CocoaPods/CocoaPods/wiki/The-podspec-format, which says that the version attribute reference should consult Semver.

Looking at the Semantic Version docs @ http://semver.org/ it says this about pre-release versions:

A pre-release version MAY be denoted by appending a dash and a series of dot separated identifiers immediately following the patch version. Identifiers MUST be comprised of only ASCII alphanumerics and dash [0-9A-Za-z-]. Pre-release versions satisfy but have a lower precedence than the associated normal version. Examples: 1.0.0-alpha, 1.0.0-alpha.1, 1.0.0-0.3.7, 1.0.0-x.7.z.92.
The version enforcement should be updated to match the specification. Pull request forthcoming...

@blakewatters blakewatters added a commit to blakewatters/Core that referenced this issue Feb 10, 2013

@blakewatters blakewatters Update CocoaPods version class to support prerelease version strings …
…that conform to the Semantic Versioning specification. fixes CocoaPods/Core#4
be56f5b
Contributor

blakewatters commented Mar 14, 2013

Fixed by merge of #5

@Ashton-W Ashton-W pushed a commit to Ashton-W/Core that referenced this issue Nov 2, 2015

@blakewatters blakewatters Update CocoaPods version class to support prerelease version strings …
…that conform to the Semantic Versioning specification. fixes CocoaPods/Core#4
a7cefd6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment