Skip to content

chore: backport v7 range parsing coverage to v6 - #924

Merged
reggi merged 1 commit into
release/v6from
reggi/chore-adds-tests-v6
Oct 20, 2026
Merged

reggi merged 1 commit into
release/v6from
reggi/chore-adds-tests-v6

Conversation

@reggi

@reggi reggi commented Oct 16, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Backport the v7 range parsing coverage from #917 to v6. Add coverage for comparator whitespace normalization, range parsing options, equality boundaries, malformed loose alternatives, long identifiers, and build metadata.

Use the same range fixture inputs and options as v7 while preserving v6-specific expected results. Tests only; no production code or dependency changes.

Stack

First of two stacked v6 backport PRs, based on release/v6. Contains test commit b381d7f. The follow-up backport of the v7 performance fix in #918 targets this branch. Merge this PR before the v6 fix.

The follow-up v6 fix is #925.

Validation

The full v6 test suite passed locally on Node 20.19.5 with 100% statement, branch, function, and line coverage; one test was skipped. The full supported Node-version matrix remains unverified locally.

Cover the same input and option matrix as v7 while keeping v6 expectations explicit.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 03b4a44c-26a3-4d56-9b26-cd46006844c6
@reggi
reggi merged commit 9a3f125 into release/v6 Oct 20, 2026
7 checks passed
@reggi
reggi deleted the reggi/chore-adds-tests-v6 branch October 20, 2026 17:07
reggi added a commit that referenced this pull request Nov 2, 2026
## Summary
Backport the v7 range parsing performance fix from #918 to v6. Replace
execution of `COMPARATORTRIM` during range parsing with a regex-free
whitespace scanner while preserving the existing exported regexes.

Preserve v6-specific parsing behavior, including numeric-first
prerelease matching. Add coverage confirming legacy compatibility,
exported regex preservation, and parsing without executing
`COMPARATORTRIM`.

## Stack
Depends on #924, the v6 coverage backport of #917. This PR targets
`reggi/chore-adds-tests-v6` so its diff contains only fix commit
`9d1812e`. Merge #924 first, then retarget this PR to `release/v6` if
GitHub does not do so automatically.

## Validation
The full v6 test suite passed locally on Node 20.19.5 with 100%
statement, branch, function, and line coverage; one test was skipped.
Additional differential checks matched the legacy regex across 30,870
cases. The full supported Node-version matrix remains unverified
locally.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 03b4a44c-26a3-4d56-9b26-cd46006844c6
@github-actions github-actions Bot mentioned this pull request Nov 2, 2026
reggi pushed a commit that referenced this pull request Nov 2, 2026
ðŸĪ– I have created a release *beep* *boop*
---


## [6.3.2](v6.3.1...v6.3.2)
(2026-11-02)
### Bug Fixes
*
[`f4ed953`](f4ed953)
[#925](#925) backport v7 range
parsing performance improvement to v6 (#925) (@reggi, @Copilot)
### Chores
*
[`9a3f125`](9a3f125)
[#924](#924) backport v7 range
parsing coverage to v6 (#924) (@reggi, @Copilot)
*
[`f623d0d`](f623d0d)
[#707](#707) deps:
`@npmcli/template-oss@4.22.0` (#707) (@lukekarrys)
*
[`ee64c7f`](ee64c7f)
[#700](#700) chore: postinstall
for dependabot template-oss PR (@lukekarrys)
*
[`0dfc8fa`](0dfc8fa)
[#624](#624) auto publish
(@lukekarrys)
*
[`5381b0c`](5381b0c)
[#842](#842) bump
@npmcli/template-oss from 4.25.1 to 4.29.0 (#842) (@dependabot[bot],
@wraithgar)
*
[`e37e8d4`](e37e8d4)
[#733](#733) postinstall for
dependabot template-oss PR (@hashtagchris)

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants