summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRaphaël Barrois <raphael.barrois@paylead.fr>2022-02-06 19:52:05 +0100
committerRaphaël Barrois <raphael.barrois@paylead.fr>2022-02-06 19:52:05 +0100
commit8a7162fc01b33964688a5be41df3865bceb875c3 (patch)
tree9741bf91c3468b585fca0109eff9476dfd7f2fd9
parentc61278bd35f2059ad3c7fc196a4b06eae34f3b7e (diff)
downloadsemantic-version-8a7162fc01b33964688a5be41df3865bceb875c3.tar.gz
docs: Update reference to NPM range specification
-rw-r--r--ChangeLog2
-rw-r--r--docs/guide.rst2
-rw-r--r--docs/reference.rst4
3 files changed, 4 insertions, 4 deletions
diff --git a/ChangeLog b/ChangeLog
index da05e60..0d30c7e 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -100,7 +100,7 @@ Backwards compatibility has been kept, but users should adjust their code for th
* Allow creation of a ``Version`` directly from parsed components, as keyword arguments
(``Version(major=1, minor=2, patch=3)``)
* Add ``Version.truncate()`` to build a truncated copy of a ``Version``
- * Add ``NpmSpec(...)``, following strict NPM matching rules (https://docs.npmjs.com/misc/semver)
+ * Add ``NpmSpec(...)``, following strict NPM matching rules (https://github.com/npm/node-semver#ranges)
* Add ``Spec.parse('xxx', syntax='<syntax>')`` for simpler multi-syntax support
* Add ``Version().precedence_key``, for use in ``sort(versions, key=lambda v: v.precedence_key)`` calls.
The contents of this attribute is an implementation detail.
diff --git a/docs/guide.rst b/docs/guide.rst
index 7780a32..9a7c5cd 100644
--- a/docs/guide.rst
+++ b/docs/guide.rst
@@ -326,7 +326,7 @@ The :class:`NpmSpec` scheme
"""""""""""""""""""""""""""
The :class:`NpmSpec` class implements the full NPM specification (from
-https://docs.npmjs.com/misc/semver.html):
+https://github.com/npm/node-semver#ranges):
.. code-block:: pycon
diff --git a/docs/reference.rst b/docs/reference.rst
index 93a29eb..6d1101b 100644
--- a/docs/reference.rst
+++ b/docs/reference.rst
@@ -336,7 +336,7 @@ In order to solve this problem, each `SemVer`_-based package management platform
python-semanticversion provides a couple of implementations of those range definition syntaxes:
- ``'simple'`` (through :class:`SimpleSpec`): A python-semanticversion specific syntax, which supports simple / intuitive patterns, and some NPM-inspired extensions;
-- ``'npm'`` (through :class:`NpmSpec`): The NPM syntax, based on https://docs.npmjs.com/misc/semver.html
+- ``'npm'`` (through :class:`NpmSpec`): The NPM syntax, based on https://github.com/npm/node-semver#ranges
- More might be added in the future.
Each of those ``Spec`` classes provides a shared set of methods to work with versions:
@@ -518,7 +518,7 @@ Each of those ``Spec`` classes provides a shared set of methods to work with ver
.. versionadded:: 2.7
- A NPM-compliant version matching engine, based on the https://docs.npmjs.com/misc/semver.html specification.
+ A NPM-compliant version matching engine, based on the https://github.com/npm/node-semver#ranges specification.
.. code-block:: pycon