Pipeline binding configuration field renamed to stream
Key Points
- pipeline → stream field renamed
- Old field deprecated but still accepted
- No runtime or binding changes
Summary
The field name inside the pipelines binding block in your Wrangler config has been renamed from pipeline to stream. The old pipeline field is deprecated but still accepted; update your config to stream to avoid deprecation warnings.
Key Points
- Replace
pipelinewithstreaminwrangler.jsonc/wrangler.tomlpipeline bindings. - No other changes required: binding names, TypeScript types, and runtime API remain the same (e.g.
env.MY_PIPELINE.send(...)). - The old
pipelinefield continues to be accepted temporarily but will produce a deprecation warning.
Example
Before (deprecated):
{
"$schema": "./node_modules/wrangler/config-schema.json",
"pipelines": [
{ "binding": "MY_PIPELINE", "pipeline": "<STREAM_ID>" }
]
}
[[pipelines]]
binding = "MY_PIPELINE"
pipeline = "<STREAM_ID>"
After (update to avoid warning):
{
"$schema": "./node_modules/wrangler/config-schema.json",
"pipelines": [
{ "binding": "MY_PIPELINE", "stream": "<STREAM_ID>" }
]
}
[[pipelines]]
binding = "MY_PIPELINE"
stream = "<STREAM_ID>"
For more information, see the documentation on writing to streams.