Merge branch 'develop' into strands_integration

Author: ronjer30

.coderabbit.yaml

@@ -123,56 +123,19 @@ reviews:
       instructions: >-
         You should only apply this label when the source branch has a name matching the regex pattern `release/\d+\.\d+`
         and the target branch is `main`.
-    - label: breaking
-      instructions: >-
-        Apply this label when the PR introduces changes that break backward compatibility, modify existing APIs in
-        incompatible ways, creates a behavioral change, or require users to update their code when upgrading. If you
-        apply this label, do not apply the "non-breaking" label. Do not apply this label if the PR already has either
-        the "breaking" or "non-breaking" label.
-    - label: bug
-      instructions: >-
-        Apply this label when the PR fixes a defect, error, or unexpected behavior in the existing codebase. If you
-        apply this label do not apply the "doc", "feature request", or "improvement" labels. Do not apply this label if
-        the PR already has either the "bug", "doc", "feature request", or "improvement" labels.
     - label: DO NOT MERGE
       instructions: >-
         Apply this label to PRs that should not be merged due to critical issues, incomplete work, or other blocking
         concerns. Check the PR description for specific details about why it should not be merged. There is no need to
         apply this label to draft PRs.
-    - label: doc
-      instructions: >-
-        Apply this label when the PR primarily adds, updates, or improves documentation including README files. If you
-        apply this label do not apply the "bug", "feature request", or "improvement" labels. Do not apply this label if
-        the PR already has either the "bug", "doc", "feature request", or "improvement" labels.
     - label: duplicate
       instructions: >-
         Apply this label when the PR addresses the same issue or implements the same feature as another existing
         PR or issue.
-    - label: external
-      instructions: >-
-        Apply this label when the PR author is not an organization OWNER or MEMBER (i.e., author_association is
-        COLLABORATOR, CONTRIBUTOR, FIRST_TIMER, FIRST_TIME_CONTRIBUTOR, or NONE).
-    - label: feature request
-      instructions: >-
-        Apply this label when the PR implements new functionality, adds new features, or introduces new capabilities
-        to the toolkit. If you apply this label do not apply the "bug", "doc", or "improvement" labels. Do not apply
-        this label if  the PR already has either the "bug", "doc", "feature request", or "improvement" labels.
-    - label: improvement
-      instructions: >-
-        Apply this label when the PR enhances existing functionality without adding completely new features, such as
-        performance optimizations, code refactoring, or usability enhancements. If you apply this label do not apply
-        the "bug", "doc", or "feature request" labels. Do not apply this label if the PR already has either the "bug",
-        "doc", "feature request", or "improvement" labels.
     - label: invalid
       instructions: >-
         Apply this label when the PR contains invalid changes, doesn't follow project guidelines, or has fundamental
         issues that make it unsuitable for the project.
-    - label: non-breaking
-      instructions: >-
-        Apply this label when the PR introduces changes that maintain backward compatibility, does not create a
-        behavioral change, and does not require users to modify their existing code. If you apply this label, do not
-        apply the "breaking" label. Do not apply this label if the PR already has either the "breaking" or
-        "non-breaking" label.
 
   tools:
     ruff:

.gitignore

@@ -211,7 +211,8 @@ tags
 [._]*.un~
 
 # Vector db files
-deploy/compose/volumes
+**/deploy/compose/volumes
+**/deploy/volumes
 examples/notebooks/examples/retail_sales_agent/deploy/volumes/
 
 # Mac Metadata

.gitlab-ci.yml

@@ -149,7 +149,15 @@ package:wheel:
       # Match  the transitional wheels
       - .tmp/wheels/nat/*/*/*.whl
     expire_in: 1 week
-
+  rules:
+    - if: $CI_CRON_NIGHTLY == "1"
+      when: always
+    - if: $CI_PIPELINE_SOURCE == 'merge_request_event'
+    - if: $CI_COMMIT_TAG
+    - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH
+    - if: $CI_COMMIT_BRANCH == 'develop-test'
+    - if: $CI_COMMIT_BRANCH == 'main'
+    - if: $CI_COMMIT_BRANCH =~ /^release\/.*$/
 
 upload:artifactory:
   stage: upload

.pre-commit-config.yaml

@@ -33,7 +33,7 @@ repos:
       - id: uv-lock
 
   - repo: https://github.com/tcort/markdown-link-check
-    rev: v3.12.2
+    rev: v3.14.1
     hooks:
       - id: markdown-link-check
         args: ["-q", "--config", "ci/markdown-link-check-config.json"]

ci/scripts/checks.sh

@@ -20,7 +20,7 @@ SCRIPT_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" &> /dev/null && pwd )"
 source ${SCRIPT_DIR}/common.sh
 
 set +e
-pre-commit run --all-files --show-diff-on-failure
+pre-commit run --show-diff-on-failure
 PRE_COMMIT_RETVAL=$?
 
 echo "Checking copyright headers"

docs/source/_static/mcp_side_panel.png

@@ -160,6 +160,7 @@ def _build_api_tree() -> Path:
 # Ignore openai.com links, as these always report a 403 when requested by the linkcheck agent
 # mysql.com  reports a 403 when requested by linkcheck
 # api.service.com is a placeholder for a service example
+# Ignore example.com/mcp as it is inaccessible when building the docs
 # Once v1.2 is merged into main, remove the ignore for the banner.png
 linkcheck_ignore = [
     r'http://localhost:\d+/',
@@ -170,6 +171,7 @@ def _build_api_tree() -> Path:
     r'https://code.visualstudio.com',
     r'https://www.mysql.com',
     r'https://api.service.com',
+    r'https?://example\.com/mcp/?',
     r'http://custom-server'
 ]
 
@@ -316,9 +318,7 @@ def _build_api_tree() -> Path:
 # -- Extension configuration -------------------------------------------------
 
 # Example configuration for intersphinx: refer to the Python standard library.
-intersphinx_mapping = {
-    "python": ('https://docs.python.org/', None), "scipy": ('https://docs.scipy.org/doc/scipy/reference', None)
-}
+intersphinx_mapping = {"python": ('https://docs.python.org/', None)}
 
 # Set the default role for interpreted code (anything surrounded in `single
 # backticks`) to be a python object. See

docs/source/_static/mcp_tools.png

@@ -147,7 +147,7 @@ Then either:
 **At runtime**, you typically see code like:
 
 ```python
-memory_client = builder.get_memory_client(<memory_config_name>)
+memory_client = await builder.get_memory_client(<memory_config_name>)
 await memory_client.add_items([MemoryItem(...), ...])
 ```
 
@@ -164,7 +164,7 @@ from nat.memory.models import MemoryItem
 from langchain_core.tools import ToolException
 
 async def add_memory_tool_action(item: MemoryItem, memory_name: str):
-    memory_client = builder.get_memory_client(memory_name)
+    memory_client = await builder.get_memory_client(memory_name)
     try:
         await memory_client.add_items([item])
         return "Memory added successfully"

docs/source/conf.py

@@ -129,6 +129,7 @@ Adding a Telemetry Exporter <./extend/telemetry-exporters.md>
 
 ./api/index.rst
 API Authentication <./reference/api-authentication.md>
+Frameworks Overview <./reference/frameworks-overview.md>
 Interactive Models <./reference/interactive-models.md>
 API Server Endpoints <./reference/api-server-endpoints.md>
 WebSockets <./reference/websockets.md>