ci: skip numpy in mypy to fix upstream stub-syntax breakage (numpy 2.5.0)

numpy 2.5.0 ships inline stubs using the 3.12 'type X = ...' statement,
which mypy can't parse under python_version 3.11, aborting the Typecheck
job on the first checked dir. vstack has no direct numpy dependency, so
add a mypy override that skips following numpy entirely. All 27 CI mypy
dirs pass locally with the override.

Author: valani9

CHANGELOG.md

@@ -39,6 +39,16 @@ thirty-six library modules and fifty CLIs shipped since v0.7.0.
   to exercise `setup_otel` but called `_otel_check_available`) with real
   `setup_otel` / `is_enabled` coverage that does not pollute global OTel
   state.
+- **CI mypy failure from upstream numpy churn** — numpy 2.5.0 (a transitive
+  dep of some framework extras) ships inline stubs using the 3.12
+  `type X = ...` statement, which mypy can't parse under `python_version
+  3.11` ("Type statement is only supported in Python 3.12 and greater").
+  Added a `[[tool.mypy.overrides]]` entry that skips following numpy, since
+  vstack has no direct numpy dependency.
+- **Docs build (strict mkdocs) had been failing since v0.36.0** — the
+  LangChain integration page linked `../composition.md#langchain`, but the
+  file lives at `concepts/composition.md`. Fixed the link so the hosted
+  docs site can deploy again.
 
 ### Changed
 

pyproject.toml

@@ -300,6 +300,16 @@ strict = true
 warn_return_any = true
 warn_unused_configs = true
 
+# numpy (a transitive dep of some optional framework extras) ships inline
+# stubs that use the 3.12 `type X = ...` statement. Because we type-check
+# against python_version 3.11, mypy can't parse those stubs and aborts
+# ("Type statement is only supported in Python 3.12 and greater"). vstack
+# does not depend on numpy directly, so skip following it entirely.
+[[tool.mypy.overrides]]
+module = ["numpy", "numpy.*"]
+follow_imports = "skip"
+follow_imports_for_stubs = true
+
 [tool.pytest.ini_options]
 minversion = "8.0"
 testpaths = [