Semantic Version Workspace

Compare, sort, normalize, and bump SemVer versions with correct prerelease precedence.

Pasted code or structured dataSemantic Version Workspace result浏览器本地处理

Loading tool…

浏览器内运行这个工具能做什么

Compare two semantic versions, sort a release list in either direction, normalize optional v-prefixed input, and calculate the next major, minor, or patch version under SemVer 2.0.0 precedence rules.

Use Sort to order a line-separated release list while keeping invalid entries visible, or Normalize & bump to remove an optional v prefix and calculate the next major, minor, and patch versions.

Build metadata is preserved in normalized output but does not affect precedence, as required by SemVer 2.0.0.

代表性任务

这个工具可以完成什么

Try a representative semantic version workspace task

Use Compare for an exact two-version precedence decision, including numeric and alphanumeric prerelease identifiers.

使用边界

依赖结果前需要检查什么

  • Performance and maximum practical input size depend on browser memory, device speed, and the structure of the input.
  • Review the generated result before replacing or publishing an original file.

如何使用

  1. 1

    Choose Compare, Sort, or Normalize & bump.

  2. 2

    Enter complete MAJOR.MINOR.PATCH versions, with optional prerelease or build metadata.

  3. 3

    Resolve any invalid entry, then copy the normalized, sorted, or bumped result.

常见问题

Does it include pre-release handling?

Yes. Pre-release precedence is handled.

What version format is expected?

Standard semver format: MAJOR.MINOR.PATCH with optional pre-release labels like 1.2.3-alpha.1.

Is 1.0 a valid input?

No. All three version parts (major, minor, patch) are required for a valid comparison.

Does build metadata change version precedence?

No. Values after + are preserved in normalized output but ignored when comparing or sorting versions, following SemVer 2.0.0.

继续当前流程

下一步常用工具

如果还需要校验、转换或复用结果,可以继续打开相近的浏览器本地工具。