chore(deps): update cft/developer-tools docker tag to v1.26

[renovate-bot]

This PR contains the following updates:

Package	Update	Change
cft/developer-tools	minor	1.25 -> 1.26

---

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: Whenever PR is behind base branch, 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 focuses on a routine dependency update, specifically upgrading the cft/developer-tools Docker image to its latest minor version, v1.26. This ensures the project utilizes the most current version of the developer tools, potentially incorporating new features, bug fixes, or performance improvements from the updated image.

Highlights

• Dependency Update: The cft/developer-tools Docker image tag has been updated from v1.25 to v1.26.
• Configuration Change: The DOCKER_TAG_VERSION_DEVELOPER_TOOLS variable in cli/Makefile was modified to reflect the new version.

🧠 New Feature in Public Preview: You can now enable Memory 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 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. ↩

[dpebot]

/gcbrun

[gemini-code-assist]

Code Review

This pull request updates the version of the cft/developer-tools Docker image from 1.25 to 1.26 in cli/Makefile. The change is correct and aligns with the goal of keeping dependencies up-to-date.

However, I noticed that the file infra/cloudbuild/test.devtools.yaml uses a hardcoded and significantly older version of the same Docker image (gcr.io/cloud-foundation-cicd/cft/developer-tools:0.5.0). This inconsistency could lead to tests being run against outdated tooling, potentially missing issues that would appear with the newer version.

While this file is outside the scope of the current changes, I recommend creating a follow-up task to investigate and update this reference for better consistency and maintainability across the repository.

[dpebot]

/gcbrun

[dpebot]

/gcbrun

[dpebot]

/gcbrun

[dpebot]

/gcbrun