chore(deps): update dependency apache-airflow-providers-google to v18

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Confidence
apache-airflow-providers-google (changelog)	==10.2.0 -> ==18.0.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[gemini-code-assist]

Summary of Changes

Hello @renovate-bot, 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 performs a significant version upgrade for the apache-airflow-providers-google dependency, moving from version 10.2.0 to 18.0.0. This update ensures that the project leverages the latest features, improvements, and security fixes provided by the Google Cloud integration for Apache Airflow, maintaining compatibility and performance with Google Cloud services.

Highlights

• Dependency Update: Updated the apache-airflow-providers-google dependency from version 10.2.0 to 18.0.0.
• Automated Maintenance: This pull request was automatically generated by Renovate bot to keep project dependencies up-to-date.

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

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

[gemini-code-assist]

Code Review

This PR updates apache-airflow-providers-google from version 10.2.0 to 18.0.0. This is a major version jump that is very likely to introduce breaking changes. The most critical issue is that the corresponding constraints.txt file has not been updated, which will lead to dependency conflicts. The DAGs using this provider should be carefully tested to ensure compatibility with the new version.

[gemini-code-assist]

While this line correctly updates the provider version, the corresponding constraints.txt file in the same directory has not been updated. It still specifies apache-airflow-providers-google==10.2.0, which will conflict with this change and likely cause dependency resolution to fail. As noted in the comment at the top of this file, the constraints file must be kept in sync.

Additionally, this is a major version upgrade from 10.2.0 to 18.0.0. Such a large jump will almost certainly include breaking changes. The DAGs in this project use operators such as DataprocCreateBatchOperator, GCSToBigQueryOperator, and BigQueryInsertJobOperator. It is crucial to review the provider's changelog and thoroughly test the DAGs to ensure they are compatible with the new version.