Changelog: go-livepeer end-of-week update for July 31

v2/resources/changelog/go-livepeer.mdx

@@ -22,7 +22,7 @@ keywords:
 'og:image:height': 630
 purpose: changelog
 audience: everyone
-lastVerified: 2026-07-30T00:00:00.000Z
+lastVerified: 2026-07-31T00:00:00.000Z
 ---
 
 import { CustomDivider } from '/snippets/components/elements/spacing/Divider.jsx'
@@ -40,6 +40,17 @@ Changes merged to [go-livepeer](https://github.com/livepeer/go-livepeer) this we
 
 <CustomDivider />
 
+<Update label="Week of July 27, 2026 (end-of-week update)" tags={["Live AI", "Live Runner", "Reliability"]} description={<Subtitle variant="changelog">July 31, 2026</Subtitle>}>
+  ## End-of-week update — July 31, 2026
+
+### Updates
+
+- **Live runners can now signal orchestrators to end streams** - Live runner heartbeat responses can now include a list of stream IDs to terminate, and the orchestrator will cleanly stop each matching Live AI pipeline (segmenter, control channel, and orchestrator-side session). This lets a runner proactively release capacity when a stream has ended, failed health checks, or should no longer be served — instead of waiting for the next payment or session-level timeout to notice. No configuration changes are required for existing runners; runners that don't return stream IDs keep the previous behavior. See the [AI pipelines guide](/v2/gateways/guides/node-pipelines/ai-pipelines) for how live runners fit into the node.
+
+</Update>
+
+<CustomDivider />
+
 <Update label="Week of July 27, 2026 (end-of-week update)" tags={["Quiet day"]} description={<Subtitle variant="changelog">July 30, 2026</Subtitle>}>
   ## End-of-week update — July 30, 2026