Dependencies update

[venkateshpabbati]

No description provided.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[gemini-code-assist]

Summary of Changes

Hello @venkateshpabbati, 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 significantly enhances the project's maintainability and security posture. It introduces automated dependency management through Dependabot, establishes a formal security policy for version support and vulnerability reporting, and updates key Python library dependencies to ensure compatibility with newer releases. Furthermore, it improves the secure handling of sensitive configuration by preventing API keys and cloud project details from being stored in .env files, promoting best practices for secret management.

Highlights

• Automated Dependency Updates: Dependabot configuration has been added to automatically check for and suggest updates for pip dependencies on a weekly basis.
• Security Policy Introduction: A new SECURITY.md file has been introduced, outlining supported versions and providing guidelines for reporting vulnerabilities.
• Dependency Version Updates: Several Python dependency version ranges in pyproject.toml have been updated, specifically for google-cloud-storage, tenacity, and langgraph, allowing for newer compatible versions.
• Enhanced Security for Environment Variables: The cli_create.py script has been modified to prevent sensitive environment variables like GOOGLE_API_KEY, GOOGLE_CLOUD_PROJECT, and GOOGLE_CLOUD_LOCATION from being written directly to .env files, instead advising users to set them manually for better security.

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

[adk-bot]

Hello @venkateshpabbati, thank you for your contribution!

Before we can proceed with reviewing this pull request, could you please address the following:

• Contributor License Agreement (CLA): It appears that the CLA has not been signed. Please sign the Google CLA to allow us to accept your contribution.
• Associated Issue: As per our contribution guidelines, all PRs (except for minor typo fixes) should have an associated GitHub issue. Could you please create an issue for this change and link it to this PR?
• Testing Plan: Could you also add a testing plan section to your PR description to explain how these changes have been tested?

This information is necessary for us to be able to review and merge your PR. You can find more details in our contribution guidelines.

Thanks!

Response from ADK Triaging Agent

[gemini-code-assist]

Code Review

This pull request updates several dependencies, adds Dependabot configuration, and introduces a security policy file. The dependency updates seem appropriate given the PR's goal. The addition of Dependabot is a good practice for keeping dependencies up-to-date automatically. The change in cli_create.py to avoid writing secrets to the .env file is an excellent security enhancement. My only suggestion is to populate the new SECURITY.md file with project-specific details to make it truly effective, for which I've provided a template.