chore: prepare Python SDK 1.4.0 release

pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "arcjet"
-version = "1.3.0"
+version = "1.4.0"
 description = "Arcjet Python SDK. Runtime security for AI applications. Prompt injection detection, bot protection, rate limiting, sensitive data detection, and WAF for Python apps."
 readme = "README.md"
 requires-python = ">=3.10"
@@ -50,7 +50,7 @@ keywords = [
 # modules, so the two are released in lockstep and must never resolve to
 # different versions (see the reciprocal pin in that package). Bump both
 # together every release.
-sensitive-info-rampart = ["arcjet-sensitive-info-rampart==1.3.0"]
+sensitive-info-rampart = ["arcjet-sensitive-info-rampart==1.4.0"]
 langchain = ["langchain-core>=1.2.5,<2"]
 # Agent middleware only. Separate from `langchain` because the full
 # `langchain` package hard-depends on LangGraph, and folding it into the

sensitive-info-rampart/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "arcjet-sensitive-info-rampart"
-version = "1.3.0"
+version = "1.4.0"
 description = "On-device Rampart NER model backend for Arcjet sensitive information detection."
 readme = "README.md"
 requires-python = ">=3.10"
@@ -12,7 +12,7 @@ dependencies = [
   # so it is coupled to the core version — release the two in lockstep. The
   # exact pin keeps this backend from ever resolving against a core whose
   # private internals it may not match; bump both together every release.
-  "arcjet==1.3.0",
+  "arcjet==1.4.0",
   "numpy>=1.24",
   # 1.23+ dropped CPython 3.10 wheels; the SDK still supports 3.10.
   # 3.14 needs a newer line (1.24+ added those wheels but dropped 3.10).