linq-python 0.24.0__tar.gz → 0.24.1__tar.gz

linq_python-0.24.1/.release-please-manifest.json

@@ -0,0 +1,3 @@
+{
+  ".": "0.24.1"
+}

{linq_python-0.24.0 → linq_python-0.24.1}/CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog
 
+## [0.24.1](https://github.com/linq-team/linq-python/compare/v0.24.0...v0.24.1) (2026-08-14)
+
+
+### Bug Fixes
+
+* clarify chat health status guidance and opt-out behavior ([17f6c3e](https://github.com/linq-team/linq-python/commit/17f6c3e46e71a0a325dcb3639444dc7423640127))
+
 ## [0.24.0](https://github.com/linq-team/linq-python/compare/v0.23.1...v0.24.0) (2026-08-14)
 
 

{linq_python-0.24.0 → linq_python-0.24.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.3
 Name: linq-python
-Version: 0.24.0
+Version: 0.24.1
 Summary: The official Python library for the linq-api-v3 API
 Project-URL: Homepage, https://github.com/linq-team/linq-python
 Project-URL: Repository, https://github.com/linq-team/linq-python

{linq_python-0.24.0 → linq_python-0.24.1}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "linq-python"
-version = "0.24.0"
+version = "0.24.1"
 description = "The official Python library for the linq-api-v3 API"
 dynamic = ["readme"]
 license = "Apache-2.0"

{linq_python-0.24.0 → linq_python-0.24.1}/src/linq/_version.py

@@ -1,4 +1,4 @@
 # File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
 
 __title__ = "linq"
-__version__ = "0.24.0"  # x-release-please-version
+__version__ = "0.24.1"  # x-release-please-version

{linq_python-0.24.0 → linq_python-0.24.1}/src/linq/types/chat.py

@@ -16,7 +16,7 @@ class HealthStatus(BaseModel):
 
     Always present — chats start at `HEALTHY` and may shift based on engagement and delivery signals on the conversation. Many `AT_RISK` or `CRITICAL` chats on a single line increase the risk of line flagging.
 
-    Switch on `status` to gate sends or surface line health in your UI — the enum is the long-term contract. Each status carries a `doc_url` that deep-links to the relevant section of the Chat Health guide.
+    Switch on `status` to surface chat and line health in your UI — the enum is the long-term contract. Each status carries a `doc_url` that deep-links to the relevant section of the Chat Health guide. To gate a send, act on the response rather than the status: a `403` is the authoritative answer.
 
     See the [Chat Health guide](/guides/chats/chat-health) for what each status means and how to react.
     """
@@ -39,6 +39,11 @@ class HealthStatus(BaseModel):
     is not itself an opt-out keyword opts them back in immediately — a reply in any
     conversation with you counts, the same way the block does.
 
+    `OPTED_OUT` marks only the conversation the keyword arrived in. The block below
+    is wider than the mark, so a conversation still reading `HEALTHY` can be blocked
+    as well — gate on the `403`, not on the status. Group threads are never marked
+    and are never blocked.
+
     Linq enforces this: while a recipient is opted out, every send to them is
     rejected with `403` (error code `2024`) before the message is queued, across
     every chat and every line on your account. Nothing is delivered, including a
@@ -78,9 +83,10 @@ class Chat(BaseModel):
     delivery signals on the conversation. Many `AT_RISK` or `CRITICAL` chats on a
     single line increase the risk of line flagging.
 
-    Switch on `status` to gate sends or surface line health in your UI — the enum is
-    the long-term contract. Each status carries a `doc_url` that deep-links to the
-    relevant section of the Chat Health guide.
+    Switch on `status` to surface chat and line health in your UI — the enum is the
+    long-term contract. Each status carries a `doc_url` that deep-links to the
+    relevant section of the Chat Health guide. To gate a send, act on the response
+    rather than the status: a `403` is the authoritative answer.
 
     See the [Chat Health guide](/guides/chats/chat-health) for what each status
     means and how to react.

{linq_python-0.24.0 → linq_python-0.24.1}/src/linq/types/chat_create_response.py

@@ -17,7 +17,7 @@ class ChatHealthStatus(BaseModel):
 
     Always present — chats start at `HEALTHY` and may shift based on engagement and delivery signals on the conversation. Many `AT_RISK` or `CRITICAL` chats on a single line increase the risk of line flagging.
 
-    Switch on `status` to gate sends or surface line health in your UI — the enum is the long-term contract. Each status carries a `doc_url` that deep-links to the relevant section of the Chat Health guide.
+    Switch on `status` to surface chat and line health in your UI — the enum is the long-term contract. Each status carries a `doc_url` that deep-links to the relevant section of the Chat Health guide. To gate a send, act on the response rather than the status: a `403` is the authoritative answer.
 
     See the [Chat Health guide](/guides/chats/chat-health) for what each status means and how to react.
     """
@@ -40,6 +40,11 @@ class ChatHealthStatus(BaseModel):
     is not itself an opt-out keyword opts them back in immediately — a reply in any
     conversation with you counts, the same way the block does.
 
+    `OPTED_OUT` marks only the conversation the keyword arrived in. The block below
+    is wider than the mark, so a conversation still reading `HEALTHY` can be blocked
+    as well — gate on the `403`, not on the status. Group threads are never marked
+    and are never blocked.
+
     Linq enforces this: while a recipient is opted out, every send to them is
     rejected with `403` (error code `2024`) before the message is queued, across
     every chat and every line on your account. Nothing is delivered, including a
@@ -76,9 +81,10 @@ class Chat(BaseModel):
     delivery signals on the conversation. Many `AT_RISK` or `CRITICAL` chats on a
     single line increase the risk of line flagging.
 
-    Switch on `status` to gate sends or surface line health in your UI — the enum is
-    the long-term contract. Each status carries a `doc_url` that deep-links to the
-    relevant section of the Chat Health guide.
+    Switch on `status` to surface chat and line health in your UI — the enum is the
+    long-term contract. Each status carries a `doc_url` that deep-links to the
+    relevant section of the Chat Health guide. To gate a send, act on the response
+    rather than the status: a `403` is the authoritative answer.
 
     See the [Chat Health guide](/guides/chats/chat-health) for what each status
     means and how to react.

{linq_python-0.24.0 → linq_python-0.24.1}/src/linq/types/chat_created_webhook_event.py

@@ -17,7 +17,7 @@ class DataHealthStatus(BaseModel):
 
     Always present — chats start at `HEALTHY` and may shift based on engagement and delivery signals on the conversation. Many `AT_RISK` or `CRITICAL` chats on a single line increase the risk of line flagging.
 
-    Switch on `status` to gate sends or surface line health in your UI — the enum is the long-term contract. Each status carries a `doc_url` that deep-links to the relevant section of the Chat Health guide.
+    Switch on `status` to surface chat and line health in your UI — the enum is the long-term contract. Each status carries a `doc_url` that deep-links to the relevant section of the Chat Health guide. To gate a send, act on the response rather than the status: a `403` is the authoritative answer.
 
     See the [Chat Health guide](/guides/chats/chat-health) for what each status means and how to react.
     """
@@ -40,6 +40,11 @@ class DataHealthStatus(BaseModel):
     is not itself an opt-out keyword opts them back in immediately — a reply in any
     conversation with you counts, the same way the block does.
 
+    `OPTED_OUT` marks only the conversation the keyword arrived in. The block below
+    is wider than the mark, so a conversation still reading `HEALTHY` can be blocked
+    as well — gate on the `403`, not on the status. Group threads are never marked
+    and are never blocked.
+
     Linq enforces this: while a recipient is opted out, every send to them is
     rejected with `403` (error code `2024`) before the message is queued, across
     every chat and every line on your account. Nothing is delivered, including a
@@ -84,9 +89,10 @@ class Data(BaseModel):
     delivery signals on the conversation. Many `AT_RISK` or `CRITICAL` chats on a
     single line increase the risk of line flagging.
 
-    Switch on `status` to gate sends or surface line health in your UI — the enum is
-    the long-term contract. Each status carries a `doc_url` that deep-links to the
-    relevant section of the Chat Health guide.
+    Switch on `status` to surface chat and line health in your UI — the enum is the
+    long-term contract. Each status carries a `doc_url` that deep-links to the
+    relevant section of the Chat Health guide. To gate a send, act on the response
+    rather than the status: a `403` is the authoritative answer.
 
     See the [Chat Health guide](/guides/chats/chat-health) for what each status
     means and how to react.

{linq_python-0.24.0 → linq_python-0.24.1}/src/linq/types/message_edited_webhook_event.py

@@ -15,7 +15,7 @@ class DataChatHealthStatus(BaseModel):
 
     Always present — chats start at `HEALTHY` and may shift based on engagement and delivery signals on the conversation. Many `AT_RISK` or `CRITICAL` chats on a single line increase the risk of line flagging.
 
-    Switch on `status` to gate sends or surface line health in your UI — the enum is the long-term contract. Each status carries a `doc_url` that deep-links to the relevant section of the Chat Health guide.
+    Switch on `status` to surface chat and line health in your UI — the enum is the long-term contract. Each status carries a `doc_url` that deep-links to the relevant section of the Chat Health guide. To gate a send, act on the response rather than the status: a `403` is the authoritative answer.
 
     See the [Chat Health guide](/guides/chats/chat-health) for what each status means and how to react.
     """
@@ -38,6 +38,11 @@ class DataChatHealthStatus(BaseModel):
     is not itself an opt-out keyword opts them back in immediately — a reply in any
     conversation with you counts, the same way the block does.
 
+    `OPTED_OUT` marks only the conversation the keyword arrived in. The block below
+    is wider than the mark, so a conversation still reading `HEALTHY` can be blocked
+    as well — gate on the `403`, not on the status. Group threads are never marked
+    and are never blocked.
+
     Linq enforces this: while a recipient is opted out, every send to them is
     rejected with `403` (error code `2024`) before the message is queued, across
     every chat and every line on your account. Nothing is delivered, including a
@@ -62,9 +67,10 @@ class DataChat(BaseModel):
     delivery signals on the conversation. Many `AT_RISK` or `CRITICAL` chats on a
     single line increase the risk of line flagging.
 
-    Switch on `status` to gate sends or surface line health in your UI — the enum is
-    the long-term contract. Each status carries a `doc_url` that deep-links to the
-    relevant section of the Chat Health guide.
+    Switch on `status` to surface chat and line health in your UI — the enum is the
+    long-term contract. Each status carries a `doc_url` that deep-links to the
+    relevant section of the Chat Health guide. To gate a send, act on the response
+    rather than the status: a `403` is the authoritative answer.
 
     See the [Chat Health guide](/guides/chats/chat-health) for what each status
     means and how to react.

{linq_python-0.24.0 → linq_python-0.24.1}/src/linq/types/message_event_v2.py

@@ -30,7 +30,7 @@ class ChatHealthStatus(BaseModel):
 
     Always present — chats start at `HEALTHY` and may shift based on engagement and delivery signals on the conversation. Many `AT_RISK` or `CRITICAL` chats on a single line increase the risk of line flagging.
 
-    Switch on `status` to gate sends or surface line health in your UI — the enum is the long-term contract. Each status carries a `doc_url` that deep-links to the relevant section of the Chat Health guide.
+    Switch on `status` to surface chat and line health in your UI — the enum is the long-term contract. Each status carries a `doc_url` that deep-links to the relevant section of the Chat Health guide. To gate a send, act on the response rather than the status: a `403` is the authoritative answer.
 
     See the [Chat Health guide](/guides/chats/chat-health) for what each status means and how to react.
     """
@@ -53,6 +53,11 @@ class ChatHealthStatus(BaseModel):
     is not itself an opt-out keyword opts them back in immediately — a reply in any
     conversation with you counts, the same way the block does.
 
+    `OPTED_OUT` marks only the conversation the keyword arrived in. The block below
+    is wider than the mark, so a conversation still reading `HEALTHY` can be blocked
+    as well — gate on the `403`, not on the status. Group threads are never marked
+    and are never blocked.
+
     Linq enforces this: while a recipient is opted out, every send to them is
     rejected with `403` (error code `2024`) before the message is queued, across
     every chat and every line on your account. Nothing is delivered, including a
@@ -77,9 +82,10 @@ class Chat(BaseModel):
     delivery signals on the conversation. Many `AT_RISK` or `CRITICAL` chats on a
     single line increase the risk of line flagging.
 
-    Switch on `status` to gate sends or surface line health in your UI — the enum is
-    the long-term contract. Each status carries a `doc_url` that deep-links to the
-    relevant section of the Chat Health guide.
+    Switch on `status` to surface chat and line health in your UI — the enum is the
+    long-term contract. Each status carries a `doc_url` that deep-links to the
+    relevant section of the Chat Health guide. To gate a send, act on the response
+    rather than the status: a `403` is the authoritative answer.
 
     See the [Chat Health guide](/guides/chats/chat-health) for what each status
     means and how to react.

{linq_python-0.24.0 → linq_python-0.24.1}/uv.lock

@@ -530,7 +530,7 @@ wheels = [
 
 [[package]]
 name = "linq-python"
-version = "0.23.1"
+version = "0.24.0"
 source = { editable = "." }
 dependencies = [
     { name = "anyio" },

linq_python-0.24.0/.release-please-manifest.json

@@ -1,3 +0,0 @@
-{
-  ".": "0.24.0"
-}