Originally created by @omeid on GitHub (Nov 1, 2014).
Build metadata MAY be denoted by appending a plus sign and a series of dot separated identifiers immediately following the patch or pre-release version. Identifiers MUST comprise only ASCII alphanumerics and hyphen [0-9A-Za-z-]. Identifiers MUST NOT be empty. Build metadata SHOULD be ignored when determining version precedence. Thus two versions that differ only in the build metadata, have the same precedence. Examples: 1.0.0-alpha+001, 1.0.0+20130313144700, 1.0.0-beta+exp.sha.5114f85.
Either, preferably . needs to be added to the allowed list of identifiers, or the example to be corrected.
Originally created by @omeid on GitHub (Nov 1, 2014).
> 1. Build metadata MAY be denoted by appending a plus sign and a series of dot separated identifiers immediately following the patch or pre-release version. **Identifiers MUST comprise only ASCII alphanumerics and hyphen [0-9A-Za-z-]**. Identifiers MUST NOT be empty. Build metadata SHOULD be ignored when determining version precedence. Thus two versions that differ only in the build metadata, have the same precedence. Examples: 1.0.0-alpha+001, 1.0.0+20130313144700, 1.0.0-beta+**exp.sha.5114f85**.
Either, preferably `.` needs to be added to the allowed list of identifiers, or the example to be corrected.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @omeid on GitHub (Nov 1, 2014).
Either, preferably
.needs to be added to the allowed list of identifiers, or the example to be corrected.@rlidwka commented on GitHub (Nov 1, 2014):
.is not a part of an identifier. It's a separator between them.