I have built my first ruby app there: https://rubygems.org/gems/youtube_dlhelper. As shown in Versions the correct versions are available: 0.1.0, 0.1.1 and 0.1.2. But it looks like rubygems lists just the oldest 0.1.0. Maybe anyone knows why?
我在那里建立了我的第一个ruby应用程序:https://rubygems.org/gems/youtube_dlhelper。如版本中所示,可以使用正确的版本:0.1.0,0.1.1和0.1.2。但看起来rubygems只列出了最早的0.1.0。也许有人知道为什么?
1 个解决方案
#1
1
The latest version of your gem is not showing up as the default because it does not conform to the Semantic Versioning specifications. Although it may seem obvious to us as humans that 0.1.2.alpha is greater than 0.1.0.alpha, a quick look at the spec shows that this is the incorrect way to specify a pre-release. Here's a relevant excerpt (emphasis added by me):
您的gem的最新版本未显示为默认值,因为它不符合语义版本控制规范。尽管对于我们来说,0.1.2.alpha大于0.1.0.alpha对我们来说似乎是显而易见的,但快速查看规范表明这是指定预释放的错误方法。这是一个相关的摘录(我强调):
A pre-release version MAY be denoted by appending a hyphen and a series of dot separated identifiers immediately following the patch version. Identifiers MUST comprise only ASCII alphanumerics and hyphen [0-9A-Za-z-]. Identifiers MUST NOT be empty. Numeric identifiers MUST NOT include leading zeroes. Pre-release versions have a lower precedence than the associated normal version. A pre-release version indicates that the version is unstable and might not satisfy the intended compatibility requirements as denoted by its 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.
可以通过在补丁版本之后紧跟附加连字符和一系列点分隔标识符来表示预发布版本。标识符必须仅包含ASCII字母数字和连字符[0-9A-Za-z-]。标识符不能为空。数字标识符不得包含前导零。预发布版本的优先级低于关联的普通版本。预发布版本表示版本不稳定,可能无法满足其关联的正常版本所表示的预期兼容性要求。示例:1.0.0-alpha,1.0.0-alpha.1,1.0.0-0.3.7,1.0.0-x.7.z.92。
I'm not exactly sure how 0.1.2.alpha is being interpreted, but I think your best bet is to release a 0.1.3 version of your gem and yank the incorrectly versioned ones. You may even try releasing a 0.1.3-alpha, but I'd wait until someone more knowledgable can a give a more definitive answer.
我不确定0.1.2.alpha是如何被解释的,但我认为你最好的办法就是发布一个0.1.3版本的宝石,然后抽出错误版本的宝石。你甚至可以尝试发布一个0.1.3-alpha,但是我会等到一个更有知识的人可以给出一个更确定的答案。
In the meantime, I'd definitely encourage you to look at the Semantic Versioning specs.
与此同时,我绝对鼓励您查看语义版本规范。
#1
1
The latest version of your gem is not showing up as the default because it does not conform to the Semantic Versioning specifications. Although it may seem obvious to us as humans that 0.1.2.alpha is greater than 0.1.0.alpha, a quick look at the spec shows that this is the incorrect way to specify a pre-release. Here's a relevant excerpt (emphasis added by me):
您的gem的最新版本未显示为默认值,因为它不符合语义版本控制规范。尽管对于我们来说,0.1.2.alpha大于0.1.0.alpha对我们来说似乎是显而易见的,但快速查看规范表明这是指定预释放的错误方法。这是一个相关的摘录(我强调):
A pre-release version MAY be denoted by appending a hyphen and a series of dot separated identifiers immediately following the patch version. Identifiers MUST comprise only ASCII alphanumerics and hyphen [0-9A-Za-z-]. Identifiers MUST NOT be empty. Numeric identifiers MUST NOT include leading zeroes. Pre-release versions have a lower precedence than the associated normal version. A pre-release version indicates that the version is unstable and might not satisfy the intended compatibility requirements as denoted by its 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.
可以通过在补丁版本之后紧跟附加连字符和一系列点分隔标识符来表示预发布版本。标识符必须仅包含ASCII字母数字和连字符[0-9A-Za-z-]。标识符不能为空。数字标识符不得包含前导零。预发布版本的优先级低于关联的普通版本。预发布版本表示版本不稳定,可能无法满足其关联的正常版本所表示的预期兼容性要求。示例:1.0.0-alpha,1.0.0-alpha.1,1.0.0-0.3.7,1.0.0-x.7.z.92。
I'm not exactly sure how 0.1.2.alpha is being interpreted, but I think your best bet is to release a 0.1.3 version of your gem and yank the incorrectly versioned ones. You may even try releasing a 0.1.3-alpha, but I'd wait until someone more knowledgable can a give a more definitive answer.
我不确定0.1.2.alpha是如何被解释的,但我认为你最好的办法就是发布一个0.1.3版本的宝石,然后抽出错误版本的宝石。你甚至可以尝试发布一个0.1.3-alpha,但是我会等到一个更有知识的人可以给出一个更确定的答案。
In the meantime, I'd definitely encourage you to look at the Semantic Versioning specs.
与此同时,我绝对鼓励您查看语义版本规范。