redis · andy-stark-redis · Jul 30, 2026 · Jul 30, 2026 · Jul 30, 2026 · Jul 30, 2026
diff --git a/HUGO_DEPENDENCY_ASSESSMENT.md b/HUGO_DEPENDENCY_ASSESSMENT.md
diff --git a/build/test_version_archiver.py b/build/test_version_archiver.py
@@ -0,0 +1,161 @@
+#!/usr/bin/env python3
+"""
+Test script for version_archiver's link versioning.
+
+When a version is archived, intra-product links must point at the frozen copy,
+not at latest. The archiver originally rewrote only `relref`, so a section
+migrated to plain Markdown links (DOC-6909) was silently left pointing at
+latest -- wrong content in an archived version, with no error or warning.
+
+These tests cover both notations, the guards they share, and the forms that must
+NOT be touched.
+"""
+
+import os
+import sys
+import tempfile
+
+# Add the build directory to the path
+sys.path.insert(0, os.path.dirname(__file__))
+
+from version_archiver import VersionArchiver
+
+
+def archive(product, version, page_relpath, content):
+    """Run the real version_relrefs() over one page in an isolated tree.
+
+    page_relpath is relative to the versioned directory, so nesting can be
+    realistic -- it matters for source-relative links, which resolve against the
+    page's own location.
+    """
+    cwd = os.getcwd()
+    with tempfile.TemporaryDirectory() as tmp:
+        arch_cwd = tmp
+        os.chdir(arch_cwd)
+        try:
+            archiver = VersionArchiver(product, version)
+            page = os.path.join(archiver.new_directory, page_relpath)
+            os.makedirs(os.path.dirname(page), exist_ok=True)
+            with open(page, "w") as f:
+                f.write(content)
+            archiver.version_relrefs()
+            with open(page) as f:
+                return f.read()
+        finally:
+            os.chdir(cwd)
+
+
+DEEP = os.path.join("databases", "configure", "page.md")
+
+
+def test_relref_is_versioned():
+    """The original behaviour: an intra-product relref gains the version."""
+    out = archive("rs", "9.9", DEEP,
+                  '[a]({{< relref "/operate/rs/databases/memory/eviction" >}})')
+    assert "/operate/rs/9.9/databases/memory/eviction" in out, out
+    print("✓ relref link is versioned")
+
+
+def test_plain_content_link_is_versioned():
+    """DOC-6909's repo-root-relative form must be versioned the same way."""
+    out = archive("rs", "9.9", DEEP,
+                  '[b](/content/operate/rs/databases/memory/eviction.md)')
+    assert "](/content/operate/rs/9.9/databases/memory/eviction.md)" in out, out
+    print("✓ plain /content/ link is versioned")
+
+
+def test_plain_content_link_keeps_anchor():
+    """An anchor must survive versioning."""
+    out = archive("rs", "9.9", DEEP,
+                  '[c](/content/operate/rs/databases/memory/eviction.md#policies)')
+    assert "/operate/rs/9.9/databases/memory/eviction.md#policies" in out, out
+    print("✓ anchor preserved when versioning a plain link")
+
+
+def test_source_relative_link_is_left_alone():
+    """Source-relative links need no rewriting and must not be touched.
+
+    The whole subtree is copied, so a link between two pages inside it already
+    resolves within the versioned directory.
+    """
+    link = '[d](../memory/eviction.md)'
+    out = archive("rs", "9.9", DEEP, link)
+    assert out == link, out
+    # and confirm the claim: it resolves inside the frozen tree
+    page_dir = os.path.join("content", "operate", "rs", "9.9",
+                            os.path.dirname(DEEP))
+    resolved = os.path.normpath(os.path.join(page_dir, "../memory/eviction.md"))
+    assert resolved.startswith(os.path.join("content", "operate", "rs", "9.9")), resolved
+    print("✓ source-relative link untouched, and resolves inside the version")
+
+
+def test_release_notes_are_exempt():
+    """Release notes are deliberately not versioned, in either notation."""
+    both = ('[e]({{< relref "/operate/rs/release-notes/rs-7-8" >}})\n'
+            '[f](/content/operate/rs/release-notes/rs-7-8.md)')
+    out = archive("rs", "9.9", DEEP, both)
+    assert out == both, out
+    print("✓ release-notes links exempt in both notations")
+
+
+def test_already_versioned_is_idempotent():
+    """Re-running must not double-version an already-versioned link."""
+    both = ('[g]({{< relref "/operate/rs/9.9/databases/memory/eviction" >}})\n'
+            '[h](/content/operate/rs/9.9/databases/memory/eviction.md)')
+    out = archive("rs", "9.9", DEEP, both)
+    assert out == both, out
+    assert "9.9/9.9" not in out, out
+    print("✓ already-versioned links are left alone (idempotent)")
+
+
+def test_other_product_and_external_urls_untouched():
+    """Only the product being archived is rewritten, and external URLs are safe.
+
+    The GitHub blob URL is the important one: it contains the substring
+    '/content/operate/rs/', so the pattern must anchor on a link destination
+    ('](/content/...') rather than matching anywhere in the line.
+    """
+    content = ('[i](/content/operate/kubernetes/deploy/quickstart.md)\n'
+               '[j](https://github.com/redis/docs/blob/main/content/operate/rs/x.md)\n'
+               '[k]({{< relref "/develop/data-types/hashes" >}})')
+    out = archive("rs", "9.9", DEEP, content)
+    assert out == content, out
+    print("✓ other products, external URLs and other sections untouched")
+
+
+def test_other_products_use_their_own_prefix():
+    """The pattern is parameterised, so non-'operate' products work too."""
+    out = archive("redis-data-integration", "1.20", DEEP,
+                  '[l](/content/integrate/redis-data-integration/reference/config.md)')
+    assert "/integrate/redis-data-integration/1.20/reference/config.md" in out, out
+    print("✓ redis-data-integration (integrate prefix) is versioned")
+
+
+def main():
+    tests = [
+        test_relref_is_versioned,
+        test_plain_content_link_is_versioned,
+        test_plain_content_link_keeps_anchor,
+        test_source_relative_link_is_left_alone,
+        test_release_notes_are_exempt,
+        test_already_versioned_is_idempotent,
+        test_other_product_and_external_urls_untouched,
+        test_other_products_use_their_own_prefix,
+    ]
+    try:
+        for t in tests:
+            t()
+        print("\n✅ All tests passed!")
+        return 0
+    except AssertionError as e:
+        print(f"\n❌ Test failed: {e}")
+        return 1
+    except Exception as e:
+        print(f"\n❌ Unexpected error: {e}")
+        import traceback
+        traceback.print_exc()
+        return 1
+
+
+if __name__ == '__main__':
+    sys.exit(main())
diff --git a/build/version_archiver.py b/build/version_archiver.py
@@ -49,6 +49,19 @@ def update_relrefs(self, file_path, version, product):
             + re.escape(product)
             + r'/([^"]+)" ?>\}\})'
         )
+        # Repo-root-relative Markdown links replace relref in sections migrated
+        # for DOC-6909, and need the same versioning. Without this they keep
+        # resolving to the latest page instead of the copy being frozen, which is
+        # silently wrong content in an archived version (no error, no warning).
+        # Source-relative links need no rewriting: the whole subtree is copied, so
+        # a link between two pages inside it already resolves within the version.
+        plain_pattern = (
+            r'(\]\(/content/'
+            + self.prefix
+            + "/"
+            + re.escape(product)
+            + r'/([^)]+)\))'
+        )
         with open(file_path, "r") as file:
             lines = file.readlines()
 
@@ -74,8 +87,12 @@ def replace_link(match):
                     return f"{new_link}"
                 return full_match
 
-            # Replace all relref links in the line
+            # Replace all relref links in the line, then the plain Markdown ones.
+            # Both share replace_link: each match contains "/<prefix>/<product>/",
+            # so the same substitution and the same release-notes and
+            # already-versioned guards apply to either notation.
             modified_line = re.sub(pattern, replace_link, lines[i])
+            modified_line = re.sub(plain_pattern, replace_link, modified_line)
 
             # If the line was modified, update the lines list
             if modified_line != lines[i]:

diff --git a/content/commands/discard.md b/content/commands/discard.md
@@ -33,7 +33,7 @@ title: DISCARD
 Flushes all previously queued commands in a [transaction][tt] and restores the
 connection state to normal.
 
-[tt]: /develop/interact/transactions
+[tt]: /develop/using-commands/transactions
 
 If [`WATCH`]({{< relref "/commands/watch" >}}) was used, `DISCARD` unwatches all keys watched by the connection.
 

diff --git a/content/commands/exec.md b/content/commands/exec.md
@@ -37,12 +37,12 @@ This command's behavior varies in clustered Redis environments. See the [multi-k
 Executes all previously queued commands in a [transaction][tt] and restores the
 connection state to normal.
 
-[tt]: /develop/interact/transactions
+[tt]: /develop/using-commands/transactions
 
 When using [`WATCH`]({{< relref "/commands/watch" >}}), `EXEC` will execute commands only if the watched keys were
 not modified, allowing for a [check-and-set mechanism][ttc].
 
-[ttc]: /develop/interact/transactions#cas
+[ttc]: /develop/using-commands/transactions#cas
 
 ## Redis Software and Redis Cloud compatibility
 

diff --git a/content/commands/expire.md b/content/commands/expire.md
@@ -104,7 +104,7 @@ Note that calling `EXPIRE`/[`PEXPIRE`]({{< relref "/commands/pexpire" >}}) with
 will be `del`, not `expired`).
 
 [del]: /commands/del
-[ntf]: /develop/use/keyspace-notifications
+[ntf]: /develop/pubsub/keyspace-notifications
 
 ## Required arguments
 

diff --git a/content/commands/multi.md b/content/commands/multi.md
@@ -38,7 +38,7 @@ This command's behavior varies in clustered Redis environments. See the [multi-k
 Marks the start of a [transaction][tt] block.
 Subsequent commands will be queued for atomic execution using [`EXEC`]({{< relref "/commands/exec" >}}).
 
-[tt]: /develop/interact/transactions
+[tt]: /develop/using-commands/transactions
 
 ## Redis Software and Redis Cloud compatibility
 

diff --git a/content/commands/setbit.md b/content/commands/setbit.md
@@ -147,7 +147,7 @@ native programming language. Symmetrically, it is also possible to set an entire
 bitmap by performing the bits-to-bytes encoding in the client and calling [`SET`]({{< relref "/commands/set" >}})
 with the resultant string.
 
-[ti]: /develop/data-types-intro#bitmaps
+[ti]: /develop/data-types#bitmaps
 
 ### Pattern: setting multiple bits
 

diff --git a/content/commands/unwatch.md b/content/commands/unwatch.md
@@ -32,7 +32,7 @@ title: UNWATCH
 ---
 Flushes all the previously watched keys for a [transaction][tt].
 
-[tt]: /develop/interact/transactions
+[tt]: /develop/using-commands/transactions
 
 If you call [`EXEC`]({{< relref "/commands/exec" >}}) or [`DISCARD`]({{< relref "/commands/discard" >}}), there's no need to manually call `UNWATCH`.
 

diff --git a/content/commands/watch.md b/content/commands/watch.md
@@ -56,7 +56,7 @@ This command's behavior varies in clustered Redis environments. See the [multi-k
 Marks the given keys to be watched for conditional execution of a
 [transaction][tt].
 
-[tt]: /develop/interact/transactions
+[tt]: /develop/using-commands/transactions
 
 ## Redis Software and Redis Cloud compatibility
 

diff --git a/content/develop/ai/redisvl/0.14.0/user_guide/sql_to_redis_queries.md b/content/develop/ai/redisvl/0.14.0/user_guide/sql_to_redis_queries.md
@@ -500,7 +500,7 @@ results
 
 ### Aggregations
 
-See docs for redis supported reducer functions: [https://redis.io/docs/latest/develop/ai/search-and-query/advanced-concepts/aggregations/#supported-groupby-reducers](docs).
+See docs for redis supported reducer functions: [docs](https://redis.io/docs/latest/develop/ai/search-and-query/advanced-concepts/aggregations/#supported-groupby-reducers).
 
 
 ```python

diff --git a/content/develop/ai/redisvl/0.23.0/user_guide/how_to_guides/mcp_authentication.md b/content/develop/ai/redisvl/0.23.0/user_guide/how_to_guides/mcp_authentication.md
@@ -19,7 +19,7 @@ authenticated.
 Authentication is a separate concern from **transport security** (Host/Origin
 validation), which is always on for the HTTP transports and defends against DNS
 rebinding independently of auth. See
-[Transport Security](mcp.md#transport-security-host-origin-validation). Both
+[Transport Security]({{< relref "mcp#transport-security-host-origin-validation" >}}). Both
 layers apply together: auth decides *who* may call; the Host/Origin guard
 rejects requests whose claimed authority is not allowlisted.
 {{< /note >}}

diff --git a/content/develop/ai/redisvl/0.6.0/user_guide/_index.md b/content/develop/ai/redisvl/0.6.0/user_guide/_index.md
@@ -84,13 +84,3 @@ User guides provide helpful resources for using RedisVL and its different compon
   * [Optimize](threshold_optimization/#optimize)
   * [Test it out](threshold_optimization/#test-it-out)
   * [Cleanup](threshold_optimization/#cleanup)
-* [Release Guides](release_guide/)
-  * [0.5.1 Feature Overview](release_guide/0_5_0_release/)
-  * [HybridQuery class](release_guide/0_5_0_release/#hybridquery-class)
-  * [TextQueries](release_guide/0_5_0_release/#textqueries)
-  * [Threshold optimization](release_guide/0_5_0_release/#threshold-optimization)
-  * [Schema validation](release_guide/0_5_0_release/#schema-validation)
-  * [Timestamp filters](release_guide/0_5_0_release/#timestamp-filters)
-  * [Batch search](release_guide/0_5_0_release/#batch-search)
-  * [Vector normalization](release_guide/0_5_0_release/#vector-normalization)
-  * [Hybrid policy on knn with filters](release_guide/0_5_0_release/#hybrid-policy-on-knn-with-filters)
diff --git a/content/develop/ai/redisvl/0.7.0/user_guide/_index.md b/content/develop/ai/redisvl/0.7.0/user_guide/_index.md
@@ -84,13 +84,3 @@ User guides provide helpful resources for using RedisVL and its different compon
   * [Optimize](threshold_optimization/#optimize)
   * [Test it out](threshold_optimization/#test-it-out)
   * [Cleanup](threshold_optimization/#cleanup)
-* [Release Guides](release_guide/)
-  * [0.5.1 Feature Overview](release_guide/0_5_0_release/)
-  * [HybridQuery class](release_guide/0_5_0_release/#hybridquery-class)
-  * [TextQueries](release_guide/0_5_0_release/#textqueries)
-  * [Threshold optimization](release_guide/0_5_0_release/#threshold-optimization)
-  * [Schema validation](release_guide/0_5_0_release/#schema-validation)
-  * [Timestamp filters](release_guide/0_5_0_release/#timestamp-filters)
-  * [Batch search](release_guide/0_5_0_release/#batch-search)
-  * [Vector normalization](release_guide/0_5_0_release/#vector-normalization)
-  * [Hybrid policy on knn with filters](release_guide/0_5_0_release/#hybrid-policy-on-knn-with-filters)
diff --git a/content/develop/ai/redisvl/user_guide/how_to_guides/mcp_authentication.md b/content/develop/ai/redisvl/user_guide/how_to_guides/mcp_authentication.md
@@ -20,7 +20,7 @@ authenticated.
 Authentication is a separate concern from **transport security** (Host/Origin
 validation), which is always on for the HTTP transports and defends against DNS
 rebinding independently of auth. See
-[Transport Security](mcp.md#transport-security-host-origin-validation). Both
+[Transport Security]({{< relref "mcp#transport-security-host-origin-validation" >}}). Both
 layers apply together: auth decides *who* may call; the Host/Origin guard
 rejects requests whose claimed authority is not allowlisted.
 {{< /note >}}

diff --git a/content/develop/ai/search-and-query/advanced-concepts/aggregations-syntax.md b/content/develop/ai/search-and-query/advanced-concepts/aggregations-syntax.md
@@ -23,10 +23,6 @@ The [main aggregations page]({{< relref "/develop/ai/search-and-query/advanced-c
 
 `GROUPBY` ... `REDUCE` ... `APPLY` ... `GROUPBY` ... `REDUCE`
 
-{{< note >}}
-The examples on this page are based on a hypothetical "products" data set, which you can [download here](./data/products.txt).
-{{< /note >}}
-
 ## Syntax and expression ordering
 
 The `FT.AGGREGATE` command processes multiple expressions in a pipeline. Below is the recommended order:

diff --git a/content/develop/clients/nodejs/amr.md b/content/develop/clients/nodejs/amr.md
@@ -155,7 +155,7 @@ authorityConfig: {
   },
 // ...
 ```
-See Microsoft's [Authority]([Authority](https://learn.microsoft.com/en-us/entra/identity-platform/msal-client-application-configuration#authority))
+See Microsoft's [Authority](https://learn.microsoft.com/en-us/entra/identity-platform/msal-client-application-configuration#authority)
 docs for more information.
 
 ### Authenticate with a service principal

diff --git a/content/develop/clients/redis-py/_index.md b/content/develop/clients/redis-py/_index.md
@@ -26,10 +26,10 @@ weight: 1
 The sections below explain how to install `redis-py` and connect your application
 to a Redis database.
 
-`redis-py` requires a running Redis server. See [here]({{< relref "/operate/oss_and_stack/install/" >}}) for Redis Open Source installation instructions.
+`redis-py` requires a running Redis server. See [here](/content/operate/oss_and_stack/install/_index.md) for Redis Open Source installation instructions.
 
 You can also access Redis with an object-mapping client interface. See
-[RedisOM for Python]({{< relref "/integrate/redisom-for-python" >}})
+[RedisOM for Python](/content/integrate/redisom-for-python/_index.md)
 for more information.
 
 ## Install

diff --git a/content/develop/clients/redis-py/amr.md b/content/develop/clients/redis-py/amr.md
@@ -26,7 +26,7 @@ letting `redis-entra-id` fetch and renew the authentication tokens for you autom
 
 ## Install
 
-Install [`redis-py`]({{< relref "/develop/clients/redis-py#install" >}}) first,
+Install [`redis-py`](/content/develop/clients/redis-py/_index.md#install) first,
 if you have not already done so. Then, install `redis-entra-id` with the
 following command:
 
@@ -134,11 +134,11 @@ When you have created your `CredentialProvider` instance, you are ready to
 connect to AMR.
 The example below shows how to pass the instance as a parameter to the standard
 `RedisCluster()` connection method.
-{{< note >}} Azure requires you to use
-[Transport Layer Security (TLS)](https://en.wikipedia.org/wiki/Transport_Layer_Security)
-when you connect (see
-[Connect with TLS]({{< relref "/develop/clients/redis-py/connect#connect-to-your-production-redis-with-tls" >}}) for more information).
-{{< /note >}}
+> [!NOTE]
+> Azure requires you to use
+> [Transport Layer Security (TLS)](https://en.wikipedia.org/wiki/Transport_Layer_Security)
+> when you connect (see
+> [Connect with TLS](/content/develop/clients/redis-py/connect.md#connect-to-your-production-redis-with-tls) for more information).
 
 ```python
 from redis import RedisCluster