Skip to content

Main content
Bookmark this: tool.io/version/semver-build-record

SemVer Build Record Extractor

Extract SemVer build identifiers as literal strings, preserving numeric-looking leading zeros without adding precedence meaning.

Loading tool…

Description

Extract SemVer build identifiers as literal strings, preserving numeric-looking leading zeros without adding precedence meaning.

Semantic versions have a major.minor.patch core, optional prerelease identifiers after a hyphen, and build identifiers after a plus. Prereleases precede the corresponding release; build metadata does not affect precedence. A textual spelling, an equal-precedence group and a major.minor release lane therefore answer different questions.1

Extract SemVer build identifiers as literal strings, preserving numeric-looking leading zeros without adding precedence meaning.

When to use this tool

Use this tool to extract SemVer build identifiers as literal strings, preserving numeric-looking leading zeros without adding precedence meaning.

How to use the tool and how it works

  1. Enter version using the field definitions below.
  2. Run the operation. Correct input errors before interpreting an output.
  3. Read result.identifiers. Use the ordering, boundary rules and absence conditions described below.

Parse one version and return its build identifiers as strings in their original order.2

Input fieldMeaning and unitsAccepted input
versionOne complete strict semantic-version string.Text, at most 8,192 UTF-16 code units; the operation’s grammar also applies.
Output fieldInterpretation
resultObject containing the named fields below.
result.identifiersOrdered prerelease or build identifiers extracted from the version.
json
{
  "input": {
    "version": "1.2.3-alpha.1+build.2"
  },
  "output": {
    "result": {
      "identifiers": [
        "build",
        "2"
      ]
    }
  }
}

Limitations and assumptions

  • Build identifiers are not converted to numbers and do not affect precedence.
  • Version text is limited to 1,024 UTF-16 code units with no whitespace. Parsed core and numeric prerelease components must be nonnegative safe integers. Range expressions and a leading v are not accepted.
  • Every declared top-level input field is required and unexpected fields are rejected. Ordinary strings are limited to 8,192 UTF-16 code units and lists to 128 entries, with tighter operation-specific bounds where stated. JSON text has bounded nesting and node counts.
  • Numeric outputs must be finite and no larger in absolute magnitude than the safe-integer limit; operations returning exact large integers use decimal text. Positions are zero-based and spans end exclusively unless the operation explicitly states a different convention.

Alternative or Complementary methods

Choose whether you need exact spelling, precedence or a release-lane grouping. Use a separate package manager or compatibility review for dependency resolution and release-policy decisions.

References

  1. Semantic Versioning 2.0.0 — Semantic Versioning

  2. Tool behavior and example: Semantic Version Build Record Extractor — tool.io

Similar or alternative tools

Support Tool.io