diff --git a/docs/manual/.buildinfo b/docs/manual/.buildinfo
index 5e56108e..6ad1058a 100644
--- a/docs/manual/.buildinfo
+++ b/docs/manual/.buildinfo
@@ -1,4 +1,4 @@
# Sphinx build info version 1
# This file records the configuration used when building these files. When it is not found, a full rebuild will be done.
-config: eeadc4cc4157f9b7fb8f04414d9f0832
+config: 3af44598b1ae08e3d831a262fbc2ecf1
tags: 645f666f9bcd5a90fca523b33c5a78b7
diff --git a/docs/manual/_sources/git.rst.txt b/docs/manual/_sources/git.rst.txt
index 43e5c8d2..0fe73ca3 100644
--- a/docs/manual/_sources/git.rst.txt
+++ b/docs/manual/_sources/git.rst.txt
@@ -817,6 +817,42 @@ You can fetch individual artifacts from a release by specifying the artifact nam
This downloads only the specified artifact and verifies its signature against the manifest. If a file already exists locally, ``rngit`` verifies it against the manifest signature and skips the download if valid, making it safe to run the command multiple times. When fetching releases, ``rngit release`` will only download files that are missing or invalid according to the manifest. This means that partially completed release fetches can be continued later, if interrupted.
+**Pattern Matching for Artifacts**
+
+When fetching selective artifacts, you are not limited to exact names or the ``all`` keyword. You can use shell-style wildcard patterns to match multiple artifacts flexibly. This is particularly useful for selecting platform-specific builds, version ranges, or file types without specifying each file individually.
+
+.. tip::
+ When using pattern matching, make sure to enclose the target specification in quotes. Otherwise,
+ your shell will probably interpret it as a shell expansion pattern *before* it is passed as an
+ argument to ``rngit``!
+
+The pattern matching supports standard Unix wildcards:
+
+- ``*`` matches any sequence of characters (including empty)
+- ``?`` matches any single character
+- ``[seq]`` matches any character in *seq* (for example ``[0-9]`` or ``[abc]``)
+- ``[!seq]`` matches any character not in *seq*
+
+For example, to fetch all wheel files for Python 3 across any platform:
+
+.. code:: text
+
+ $ rngit release rns://remote_node/public/myrepo fetch "1.2.0:*-py3-*.whl"
+
+To fetch a specific patch version when you know the major and minor version:
+
+.. code:: text
+
+ $ rngit release rns://remote_node/public/myrepo fetch "1.2.0:myapp-1.2.?-linux-x86_64.tar.gz"
+
+Or to retrieve all source archives:
+
+.. code:: text
+
+ $ rngit release rns://remote_node/public/myrepo fetch "1.2.0:source_*.tgz"
+
+If your pattern contains no wildcard characters, it must match an artifact name exactly, which is useful for fetching single, specific artifacts. When a pattern matches multiple artifacts, all matched files are fetched and verified. If no artifacts match the pattern, the fetch aborts with an error indicating no matches were found.
+
**Offline Verification**
Because the release manifest contains embedded signatures, you can verify the integrity of release artifacts offline, without connecting to the repository node. The ``rnid`` and ``rngit`` utilities can validate artifact signatures against ``.rsg`` and manifest files.
diff --git a/docs/manual/_static/documentation_options.js b/docs/manual/_static/documentation_options.js
index 92c583fb..23729927 100644
--- a/docs/manual/_static/documentation_options.js
+++ b/docs/manual/_static/documentation_options.js
@@ -1,5 +1,5 @@
const DOCUMENTATION_OPTIONS = {
- VERSION: '1.2.9',
+ VERSION: '1.3.0',
LANGUAGE: 'en',
COLLAPSE_INDEX: false,
BUILDER: 'html',
diff --git a/docs/manual/distributed.html b/docs/manual/distributed.html
index d04420ea..e4551f3a 100644
--- a/docs/manual/distributed.html
+++ b/docs/manual/distributed.html
@@ -7,7 +7,7 @@
Distributed Development - Reticulum Network Stack 1.2.9 documentation
+ Distributed Development - Reticulum Network Stack 1.3.0 documentation
Code Examples - Reticulum Network Stack 1.2.9 documentation
+ Code Examples - Reticulum Network Stack 1.3.0 documentation
An Explanation of Reticulum for Human Beings - Reticulum Network Stack 1.2.9 documentation
+ An Explanation of Reticulum for Human Beings - Reticulum Network Stack 1.3.0 documentation
Index - Reticulum Network Stack 1.2.9 documentation
+ Index - Reticulum Network Stack 1.3.0 documentation
Getting Started Fast - Reticulum Network Stack 1.2.9 documentation
+ Getting Started Fast - Reticulum Network Stack 1.3.0 documentation
Git Over Reticulum - Reticulum Network Stack 1.2.9 documentation
+ Git Over Reticulum - Reticulum Network Stack 1.3.0 documentation
This downloads only the specified artifact and verifies its signature against the manifest. If a file already exists locally, rngit rngit release
+Pattern Matching for Artifacts
+When fetching selective artifacts, you are not limited to exact names or the all
+
+
Tip
+
When using pattern matching, make sure to enclose the target specification in quotes. Otherwise,
+your shell will probably interpret it as a shell expansion pattern before it is passed as an
+argument to rngit
+
The pattern matching supports standard Unix wildcards:
+
+*
?
[seq] seq (for example [0-9] [abc]
[!seq] seq
+For example, to fetch all wheel files for Python 3 across any platform:
+
+
To fetch a specific patch version when you know the major and minor version:
+
+
Or to retrieve all source archives:
+
+
If your pattern contains no wildcard characters, it must match an artifact name exactly, which is useful for fetching single, specific artifacts. When a pattern matches multiple artifacts, all matched files are fetched and verified. If no artifacts match the pattern, the fetch aborts with an error indicating no matches were found.
Offline Verification
Because the release manifest contains embedded signatures, you can verify the integrity of release artifacts offline, without connecting to the repository node. The rnid rngit .rsg
For individual files:
@@ -1446,7 +1474,7 @@ options:
-
+
diff --git a/docs/manual/hardware.html b/docs/manual/hardware.html
index 0ca5c4c9..27883302 100644
--- a/docs/manual/hardware.html
+++ b/docs/manual/hardware.html
@@ -7,7 +7,7 @@
Communications Hardware - Reticulum Network Stack 1.2.9 documentation
+ Communications Hardware - Reticulum Network Stack 1.3.0 documentation
Reticulum Network Stack 1.2.9 documentation
+ Reticulum Network Stack 1.3.0 documentation
Configuring Interfaces - Reticulum Network Stack 1.2.9 documentation
+ Configuring Interfaces - Reticulum Network Stack 1.3.0 documentation
Reticulum License - Reticulum Network Stack 1.2.9 documentation
+ Reticulum License - Reticulum Network Stack 1.3.0 documentation
Building Networks - Reticulum Network Stack 1.2.9 documentation
+ Building Networks - Reticulum Network Stack 1.3.0 documentation
API Reference - Reticulum Network Stack 1.2.9 documentation
+ API Reference - Reticulum Network Stack 1.3.0 documentation
Search - Reticulum Network Stack 1.2.9 documentation Search - Reticulum Network Stack 1.3.0 documentation Programs Using Reticulum - Reticulum Network Stack 1.2.9 documentation
+ Programs Using Reticulum - Reticulum Network Stack 1.3.0 documentation
Support Reticulum - Reticulum Network Stack 1.2.9 documentation
+ Support Reticulum - Reticulum Network Stack 1.3.0 documentation
Understanding Reticulum - Reticulum Network Stack 1.2.9 documentation
+ Understanding Reticulum - Reticulum Network Stack 1.3.0 documentation
Using Reticulum on Your System - Reticulum Network Stack 1.2.9 documentation
+ Using Reticulum on Your System - Reticulum Network Stack 1.3.0 documentation
What is Reticulum? - Reticulum Network Stack 1.2.9 documentation
+ What is Reticulum? - Reticulum Network Stack 1.3.0 documentation
Zen of Reticulum - Reticulum Network Stack 1.2.9 documentation
+ Zen of Reticulum - Reticulum Network Stack 1.3.0 documentation
