SEARCH-3214 : merge origin/main into release/3.x

.safety-policy.yml

@@ -11,10 +11,9 @@ security: # configuration for the `safety check` command
             reason: The maintainer and multiple third parties believe that this vulnerability isn't valid because users shouldn't use untrusted templates without sandboxing.
         96886:
             reason: Fix requires urllib3>=2.7.0, which dropped Python 3.9 support. This project still supports Python 3.9 (see pyproject.toml), so the fixed version cannot be installed on that interpreter. Revisit when Python 3.9 support is dropped. NOTE this entry is superseded in CI, where -i flags on the safety check command are used instead for this and related IDs (see .github/workflows/security.yml) since -i replaces rather than merges with this list when both are passed.
-        SFTY-20260803-49978:
-            reason: Fix requires aiohttp>=3.14.3, which dropped Python 3.9 support (Requires-Python >=3.10). This project still supports Python 3.9 (see pyproject.toml), so the py3.9 aiohttp constraint (<3.14) cannot pick up the fix. Revisit when Python 3.9 support is dropped. NOTE this entry is superseded in CI, where -i flags on the safety check command are used instead for this and related IDs (see .github/workflows/security.yml) since -i replaces rather than merges with this list when both are passed.
-        SFTY-20260803-85786:
-            reason: Fix requires aiohttp>=3.14.2, which dropped Python 3.9 support (Requires-Python >=3.10). This project still supports Python 3.9 (see pyproject.toml), so the py3.9 aiohttp constraint (<3.14) cannot pick up the fix. Revisit when Python 3.9 support is dropped. NOTE this entry is superseded in CI, where -i flags on the safety check command are used instead for this and related IDs (see .github/workflows/security.yml) since -i replaces rather than merges with this list when both are passed.
-        SFTY-20260803-45259:
-            reason: Fix requires aiohttp>=3.14.2, which dropped Python 3.9 support (Requires-Python >=3.10). This project still supports Python 3.9 (see pyproject.toml), so the py3.9 aiohttp constraint (<3.14) cannot pick up the fix. Revisit when Python 3.9 support is dropped. NOTE this entry is superseded in CI, where -i flags on the safety check command are used instead for this and related IDs (see .github/workflows/security.yml) since -i replaces rather than merges with this list when both are passed.
+        # SFTY-20260803-49978, SFTY-20260803-85786 and SFTY-20260803-45259 (aiohttp, same Python 3.9
+        # rationale as above) are intentionally NOT listed here: the installed safety version (2.3.5)
+        # only accepts integer vulnerability IDs under ignore-vulnerabilities and fails to load this
+        # whole policy file otherwise. They are ignored via -i flags in the CI workflows instead
+        # (see .github/workflows/security.yml and .github/workflows/cve-scanning-python.yml).
     continue-on-vulnerability-error: False # Suppress non-zero exit codes when vulnerabilities are found. Enable this in pipelines and CI/CD processes if you want to pass builds that have vulnerabilities

examples/services/messages.py

@@ -9,7 +9,7 @@
 from symphony.bdk.gen.agent_model.message_search_query import MessageSearchQuery
 from symphony.bdk.gen.agent_model.v4_imported_message import V4ImportedMessage
 from symphony.bdk.gen.agent_model.v4_imported_message_attachment import V4ImportedMessageAttachment
-from symphony.bdk.core.service.stream.stream_util import to_url_safe_stream_id
+
 
 async def run():
     stream_id_1 = "lRwCZlDbxWLd2BDP-1D_8n___o0f4ZkEdA"