[DO NOT MERGE] Run all PostCommit and PreCommit Tests against Release Branch

[Amar3tto]

Tests run on GHA should be queued shortly.

[gemini-code-assist]

Summary of Changes

Hello @Amar3tto, 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 is a temporary, non-mergeable change designed to facilitate the execution of all PostCommit and PreCommit tests against a designated release branch. The changes include the addition of an empty JSON file, which likely acts as a trigger for the testing workflow, and a minor version update for Apache Beam within a SQL-related script. The primary purpose is to queue and run these tests on GitHub Actions.

Highlights

• Test Trigger: Introduced a new, empty JSON file at "release/trigger_all_tests.json". This file likely serves as a trigger for CI/CD pipelines to initiate comprehensive PostCommit and PreCommit tests against a release branch, as indicated by the PR title.
• Dependency Update: Updated the "DEFAULT_BEAM_VERSION" in "scripts/beam-sql.sh" from "2.67.0" to "2.69.0", reflecting a minor version bump for Apache Beam.

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 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 counter productive. 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.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

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. ↩

[github-actions]

Test Results

15 tests   15 ✅  1h 36m 53s ⏱️
12 suites   0 💤
12 files     0 ❌

Results for commit 82d1130.

[github-actions]

Checks are failing. Will not request review until checks are succeeding. If you'd like to override that behavior, comment assign set of reviewers