Description
Add or remove a lowercase v on a restricted release version.
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.
Add or remove a lowercase v on a restricted release version.
When to use this tool
Use Development: Release Version V Prefix Policy when checking one explicit version-token or core-bound convention.
How to use the tool and how it works
- Enter version, policy. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read result. Expand result to inspect the returned fields.
Add or remove a lowercase v on a restricted release version. Accept optional single v followed by three canonical decimal components and policy require-v or remove-v; report hadPrefix.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| version | Supplied version label, compared literally where stated. | Required. Text. Implementation limit: 8192 Unicode code points and 16384 UTF-16 code units. |
| policy | Policy | Required. Text; one of "require-v", "remove-v". Implementation limit: 8192 Unicode code points and 16384 UTF-16 code units. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| result | Returned object; expand its named members below. | Required. Object. |
| result.version | Supplied version label, compared literally where stated. | Calculated result member: string. |
| result.hadPrefix | Had Prefix | Calculated result member: boolean. |
{
"input": {
"version": "v1.2.3",
"policy": "remove-v"
},
"output": {
"result": {
"version": "1.2.3",
"hadPrefix": true
}
}
}Limitations and assumptions
- Prerelease and build suffixes are rejected; prefix handling is presentation policy, not core SemVer grammar.
- Outputs are nested inside result. 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
Similar or alternative tools
- Development: SemVer Build Identifier Format
Inspect one build-identifier spelling.
- SemVer Build Metadata Identifiers
Split validated build metadata into identifiers.