[#38708] Add Flink 2.0 to SDK pipeline options validation lists

[durgaprasadml]

What does this PR do?

This PR fixes the Flink 2.0 CLI validation mismatch reported in #38708.

Beam 2.72.0 already includes Flink 2.0 runner support and the documentation reflects this, but the SDK option validation lists were not updated accordingly.

As a result, passing:

bash --flink_version 2.0

failed with:

text invalid choice: '2.0'

Changes

• Added 2.0 to PUBLISHED_FLINK_VERSIONS in:

  • sdks/python/apache_beam/options/pipeline_options.py
  • sdks/typescript/src/apache_beam/runners/flink.ts

• Updated default CI Flink version metadata:

  • .github/actions/setup-default-test-properties/test-properties.json

Verification

Validated locally with:

bash python -c "from apache_beam.options.pipeline_options import PipelineOptions, FlinkRunnerOptions; opts = PipelineOptions(['--runner=FlinkRunner', '--flink_version=2.0']); print(opts.view_as(FlinkRunnerOptions).flink_version)"

which now parses successfully and returns:

text 2.0

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a validation mismatch where Flink 2.0 was not recognized as a valid version in the SDK pipeline options despite being supported by the runner. By updating the allowed version lists across the Python and TypeScript SDKs and the CI test properties, users can now successfully specify Flink 2.0 in their pipeline configurations.

Highlights

• Flink 2.0 Support: Added Flink 2.0 to the supported versions list in Python and TypeScript SDK pipeline options to resolve validation errors.
• CI Configuration Update: Updated the default test properties in the CI configuration to include Flink 2.0 for testing.

New Features

🧠 You can now enable Memory (public preview) to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds support for Flink version 2.0 by updating the supported and published Flink versions in the test properties, Python pipeline options, and TypeScript Flink runner configuration. No review comments were provided, so there is no feedback to address.