From da55cf15dd71a0d9a839e7507e4fc69396c8326d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Rapha=C3=ABl=20Barrois?= <raphael.barrois@polyconseil.fr>
Date: Thu, 21 Nov 2019 12:45:28 +0100
Subject: Fix NpmSpec prerelease-handling.

Thanks to Nathan Walters for spotting this.

Npm ranges with a `<X.Y.Z-P` component were not properly expanded:
they were converted to:
    <X.Y.0 || (>=X.Y.0 && <X.Y.Z-P && no-prerelease)

The correct expansion is:
    <X.Y.0 || (>=X.Y.0-* && <X.Y.Z-P)

Closes #86.
---
 semantic_version/base.py | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

(limited to 'semantic_version')

diff --git a/semantic_version/base.py b/semantic_version/base.py
index 4327fa1..1b0bac5 100644
--- a/semantic_version/base.py
+++ b/semantic_version/base.py
@@ -1273,7 +1273,7 @@ class NpmSpec(BaseSpec):
                                 prerelease_policy=Range.PRERELEASE_ALWAYS,
                             ))
                         elif clause.operator in (Range.OP_LT, Range.OP_LTE):
-                            prerelease_clauses.append(cls.range(
+                            prerelease_clauses.append(Range(
                                 operator=Range.OP_GTE,
                                 target=Version(
                                     major=clause.target.major,
@@ -1281,6 +1281,7 @@ class NpmSpec(BaseSpec):
                                     patch=0,
                                     prerelease=(),
                                 ),
+                                prerelease_policy=Range.PRERELEASE_ALWAYS,
                             ))
                         prerelease_clauses.append(clause)
                         non_prerel_clauses.append(cls.range(
-- 
cgit v1.2.1