Files
Michael Kriese c23e9f0fe5 test: close remaining line coverage gaps (#45870)
* test: close remaining line coverage gaps

A full coverage run reported three uncovered lines:

- `rez` versioning: `rez2pep440()` was never called with a plain version,
  because `getNewValue()` short-circuits via `matchVersionPrecision()`
  whenever the new version is valid for npm. A four-component rez version
  is not, so it reaches the pep440 path.
- `nuget` v3: only the inner nuspec 404 was covered, never a 404 escaping
  from the `.nupkg` download into the outer catch.
- `github` platform: the statement after `await` in the GitHub App branch
  is a v8/source-map false negative - it runs, but is counted zero. The
  branch used to carry the `v8 ignore` comment, which moved away with the
  `ghHostname` block in #44587.

Co-Authored-By: Claude Opus 5 <michael.kriese+claude-code@mend.io>

* build: ratchet coverage thresholds

A full run now reports 100% statements (49776/49776), 100% lines
(49256/49256), 100% functions and 98.72% branches (25756/26089), so the
thresholds move up accordingly. Branches keep the same rounding-down
margin as before.

Co-Authored-By: Claude Opus 5 <michael.kriese+claude-code@mend.io>

---------

Co-authored-by: Claude Opus 5 <michael.kriese+claude-code@mend.io>
2026-09-11 10:03:46 +00:00
..
2022-03-04 09:04:02 +01:00

rez versioning was developed to support the rez Package Manager. It's based on Semantic Versioning but includes its own concept of ranges.

Use of dots

A range is expressed with dots 1.2..2 means >=1.2.x <2.0.0.

No exact versions unless using two equals ==

In rez, 1.2.3 doesn't mean "exactly 1.2.3", it actually means >= 1.2.3 <1.2.4. If you want to use an exact version use two equal characters, like this: ==1.2.3.

Use of pipes

rez uses pipes as an OR operator, 2.7..3|4 means >=2.7 <3 OR 4.x.x.

This has not been implemented yet. The current iteration of rez versioning does not support pipes yet.