From 18668f76e7e22b9a0db92a2d41cfa4221ed892ea Mon Sep 17 00:00:00 2001
From: Marc Selwan <marc@marcinthecloud.com>
Date: Fri, 8 May 2026 07:13:18 -0700
Subject: [PATCH] [Pipelines] Rename pipeline field to stream in binding
 configuration

---
 ...26-05-08-pipeline-binding-stream-field.mdx | 52 +++++++++++++++++++
 .../pipelines/streams/writing-to-streams.mdx  |  8 ++-
 2 files changed, 58 insertions(+), 2 deletions(-)
 create mode 100644 src/content/changelog/pipelines/2026-05-08-pipeline-binding-stream-field.mdx

diff --git a/src/content/changelog/pipelines/2026-05-08-pipeline-binding-stream-field.mdx b/src/content/changelog/pipelines/2026-05-08-pipeline-binding-stream-field.mdx
new file mode 100644
index 000000000000000..c609a50ef5991f2
--- /dev/null
+++ b/src/content/changelog/pipelines/2026-05-08-pipeline-binding-stream-field.mdx
@@ -0,0 +1,52 @@
+---
+title: Pipeline binding configuration field renamed to stream
+description: The pipeline field in Wrangler pipeline binding configuration has been renamed to stream. The old field is deprecated but still accepted.
+products:
+  - pipelines
+  - workers
+date: 2026-05-08
+---
+
+import { WranglerConfig } from "~/components";
+
+The `pipeline` field inside the `pipelines` binding configuration in your [Wrangler configuration file](/workers/wrangler/configuration/) has been renamed to `stream`. The old field is deprecated but still accepted.
+
+Update your configuration to use `stream` to avoid the deprecation warning.
+
+**Before (deprecated):**
+
+<WranglerConfig>
+
+```jsonc
+{
+	"pipelines": [
+		{
+			"binding": "MY_PIPELINE",
+			"pipeline": "<STREAM_ID>"
+		}
+	]
+}
+```
+
+</WranglerConfig>
+
+**After:**
+
+<WranglerConfig>
+
+```jsonc
+{
+	"pipelines": [
+		{
+			"binding": "MY_PIPELINE",
+			"stream": "<STREAM_ID>"
+		}
+	]
+}
+```
+
+</WranglerConfig>
+
+No other changes are required. The binding name, TypeScript types, and runtime API (`env.MY_PIPELINE.send(...)`) remain the same.
+
+For more information on configuring pipeline bindings, refer to [Writing to streams](/pipelines/streams/writing-to-streams/#configure-pipeline-binding).
diff --git a/src/content/docs/pipelines/streams/writing-to-streams.mdx b/src/content/docs/pipelines/streams/writing-to-streams.mdx
index bbf6e66cdcb2c44..fc6662bbb20393d 100644
--- a/src/content/docs/pipelines/streams/writing-to-streams.mdx
+++ b/src/content/docs/pipelines/streams/writing-to-streams.mdx
@@ -25,14 +25,18 @@ Add a pipeline binding to your Wrangler file that points to your stream:
 {
 	"pipelines": [
 		{
-			"pipeline": "<STREAM_ID>",
-			"binding": "STREAM"
+			"binding": "STREAM",
+			"stream": "<STREAM_ID>"
 		}
 	]
 }
 ```
 </WranglerConfig>
 
+:::note
+The `pipeline` field in the `pipelines` binding configuration has been renamed to `stream`. Existing configurations that use `pipeline` will continue to work, but Wrangler will display a deprecation warning. Update your configuration to use `stream` instead.
+:::
+
 ### Workers API
 
 The pipeline binding exposes a method for sending data to your stream: