[Feature Request]: I want to fix the beam version when using beam yaml

[ZwxwZ]

What would you like to happen?

In Beam YAML,
There have risk if the program always using the latest version of beam,
I want to control by myself,
are there have any feature about that?

Issue Priority

Priority: 2 (default / most feature requests should be filed as P2)

Issue Components

• Component: Python SDK
• Component: Java SDK
• Component: Go SDK
• Component: Typescript SDK
• Component: IO connector
• Component: Beam YAML
• Component: Beam examples
• Component: Beam playground
• Component: Beam katas
• Component: Website
• Component: Infrastructure
• Component: Spark Runner
• Component: Flink Runner
• Component: Samza Runner
• Component: Twister2 Runner
• Component: Hazelcast Jet Runner
• Component: Google Cloud Dataflow Runner

[claudevdm]

How are you launching this job?

If using gcloud cli you can control the SDK version by specifying the template file location like

gcloud dataflow yaml run pipeline-yaml   --yaml-pipeline-file=pipeline.yaml   --region=us-central1 --template-file-gcs-location=gs://dataflow-templates-us-central1/2025-09-10-00_RC00/flex/Yaml_Template

[ZwxwZ]

How are you launching this job?

If using gcloud cli you can control the SDK version by specifying the template file location like

gcloud dataflow yaml run pipeline-yaml   --yaml-pipeline-file=pipeline.yaml   --region=us-central1 --template-file-gcs-location=gs://dataflow-templates-us-central1/2025-09-10-00_RC00/flex/Yaml_Template

yes, i‘m using gcloud, but where i can set the specific version for apache beam?
the command is only about template, right?

[claudevdm]

As long as you launch jobs with a static temlate file the sdk version will stay constant. For example, 2025-09-10-00_RC00 uses sdk version 2.67

Unfortunately there isnt an easy way to tell what template file corresponds to what sdk version. But the date of the template file should be close to the latest released sdk version at that date (on 2025-09-10 the latest sdk version was 2.67)