SemVer Build Metadata Identifiers Tool

Description

Split validated build metadata into identifiers.

Semantic versions separate core numbers, prerelease identifiers and build metadata. Numeric prerelease leading zeros are restricted while build identifiers preserve text; local identifier or bound checks do not implement complete dependency-range resolution.

Split validated build metadata into identifiers.

When to use this tool

Use SemVer Build Metadata Identifiers when checking one explicit version-token or core-bound convention.

How to use the tool and how it works

Enter metadata. Use the units and conventions below.
Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
Read identifiers. Use the output convention below.

Split validated build metadata into identifiers. Require nonempty dot-separated ASCII alphanumeric/hyphen components; return them in order as strings.^[1]

Numeric prerelease identifiers exclude leading zeros; build metadata identifiers can retain them and do not affect version precedence.^[2]

Input field	Meaning and units	Accepted input
metadata	Metadata	Required. Text; maximum UTF-16 length 8192.

Output field	Interpretation	Returned shape
identifiers	Identifiers	Required. Array of text; maximum UTF-16 length 8192; maximum items 256.

json

{
  "input": {
    "metadata": "build.001.sha-abc"
  },
  "output": {
    "identifiers": [
      "build",
      "001",
      "sha-abc"
    ]
  }
}

Limitations and assumptions

Leading zeros are preserved; build metadata has no SemVer precedence effect.
Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Use a conforming full version/range implementation and package-manager resolution when compatibility or installation is the question.

References

Calculation and input contract: development/semver-build-metadata-identifiers — tool.io
Semantic Versioning 2.0.0 — Semantic Versioning

Similar or alternative tools

Development: SemVer Build Identifier Format
Inspect one build-identifier spelling.
Development: SemVer Prerelease Identifier Kind
Classify one valid prerelease identifier as numeric or alphanumeric.