Semantic Version Range Checker
Check a semantic version against a whitespace-joined AND set of comparators (=, <, <=, >, >= plus caret ^ and tilde ~ shorthands with npm-style bump rules); build metadata is ignored.
Description
Check a semantic version against a whitespace-joined AND set of comparators (=, <, <=, >, >= plus caret ^ and tilde ~ shorthands with npm-style bump rules); build metadata is ignored.
Semantic Version Range Checker: Check a semantic version against a whitespace-joined AND set of comparators (=, <, <=, >, >= plus caret ^ and tilde ~ shorthands with npm-style bump rules); build metadata is ignored.
When to use Semantic Version Range
Use this semantic-version operation to compare or test versions that follow the SemVer major.minor.patch grammar and its prerelease precedence rules.
- Range
- Whitespace-separated comparators, e.g. "^1.2.0 <2.0.0".
- Version
- Version to test against the range.
How Semantic Version Range works
Check a semantic version against a whitespace-joined AND set of comparators (=, <, <=, >, >= plus caret ^ and tilde ~ shorthands with npm-style bump rules); build metadata is ignored. The tool evaluates the supplied inputs together and returns the named outputs below; it does not infer omitted operating conditions or change the units shown.1
- Satisfied
- True when the version satisfies every comparator.
- Comparator count
- Number of primitive comparators after expanding ^ and ~.
Limitations and assumptions
- Semantic Versioning describes version syntax and declared compatibility intent; it does not prove that releases are compatible. Ecosystems may use different range grammars, leading zeros, build metadata, prerelease inclusion rules, or non-SemVer versions.
- Use finite inputs in the displayed units and preserve more precision than the final presentation requires. Independently verify safety-critical, financial, compliance, or production decisions.
Alternative or Complementary approaches
Use the package ecosystem's own resolver before changing a lockfile, and confirm compatibility with tests and release notes. Keep version comparison separate from lexical string ordering.
References
-
Software versioning — Wikipedia contributors
Similar or alternative tools
- Semantic Version Comparator
Compare two semantic versions exactly per semver.org precedence: numeric major.minor.patch, prerelease identifier rules, and build metadata ignored.
- Additional Handling Fee Trigger Checker
Check a rectangular parcel against configurable longest-side, second-longest-side, actual-weight, and length-plus-girth thresholds; packaging and service-specific rules are outside this numeric screen.
- Absolute Refractory Check
Check whether a neuron is inside its absolute refractory period by comparing elapsed time since the last spike against the absolute refractory window.