From d48b0876d5b771d9cb003c80f6424233bc784237 Mon Sep 17 00:00:00 2001
From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com>
Date: Sat, 25 Jul 2026 00:09:13 +0000
Subject: [PATCH] docs: add go-livepeer changelog entry for July 25, 2026

---
 v2/resources/changelog/go-livepeer.mdx | 17 ++++++++++++++++-
 1 file changed, 16 insertions(+), 1 deletion(-)

diff --git a/v2/resources/changelog/go-livepeer.mdx b/v2/resources/changelog/go-livepeer.mdx
index 5f6d38a75..92d5c392e 100644
--- a/v2/resources/changelog/go-livepeer.mdx
+++ b/v2/resources/changelog/go-livepeer.mdx
@@ -22,7 +22,7 @@ keywords:
 'og:image:height': 630
 purpose: changelog
 audience: everyone
-lastVerified: 2026-07-24T00:00:00.000Z
+lastVerified: 2026-07-25T00:00:00.000Z
 ---
 
 import { CustomDivider } from '/snippets/components/elements/spacing/Divider.jsx'
@@ -40,6 +40,21 @@ Changes merged to [go-livepeer](https://github.com/livepeer/go-livepeer) this we
 
 <CustomDivider />
 
+<Update label="Week of July 20, 2026 (weekend update)" tags={["Live Runner", "Payments", "Pricing"]} description={<Subtitle variant="changelog">July 25, 2026</Subtitle>}>
+  ## Weekend update — July 25, 2026
+
+### New features
+
+- **Fixed pricing for live runners** - Orchestrators can now advertise a `fixed` price for live runner apps, charging a single payment when a session or request is created instead of metering payment over time or processed pixels. Fixed pricing flows end-to-end through static and dynamic runner registration, discovery, remote signers, and orchestrator accounting, so gateways and clients see the price and pay once at session start. Existing time- and pixel-metered runners are unaffected. See the [AI pipelines guide](/v2/gateways/guides/node-pipelines/ai-pipelines) for how live runners fit into the node.
+
+### Updates
+
+- **Single-shot live runner sessions now enforce payments** - Requests to the single-shot proxy path now go through the standard `402 Payment Required` challenge and are subject to the same payment accounting as persistent sessions. Previously, single-shot requests were proxied without a payment check, which meant operators had to use persistent mode to enforce on-chain payment. Combined with fixed pricing, this makes single-shot mode a first-class option for stateless request/response and fast batch inference workloads. Fixed-payment sessions still only need to pay once at reservation. See the [AI pipelines guide](/v2/gateways/guides/node-pipelines/ai-pipelines) for background on live runner sessions.
+
+</Update>
+
+<CustomDivider />
+
 <Update label="Week of July 20, 2026 (weekend update)" tags={["Quiet day"]} description={<Subtitle variant="changelog">July 24, 2026</Subtitle>}>
   ## Weekend update — July 24, 2026