chore(deps): update mcr.microsoft.com/devcontainers/universal docker tag to v5

[renovate-bot]

This PR contains the following updates:

Package	Type	Update	Change
mcr.microsoft.com/devcontainers/universal	image	major	2 → 5

---

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 becomes conflicted, 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 updates the base Docker image used for the devcontainer configuration. By upgrading the mcr.microsoft.com/devcontainers/universal image to its latest major version, v5, the development environment benefits from the most recent features, improvements, and security patches, ensuring a modern and consistent setup for all contributors.

Highlights

• Docker Image Update: The mcr.microsoft.com/devcontainers/universal Docker image tag has been updated from v2 to v5.

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

[gemini-code-assist]

Code Review

This pull request, generated by Renovate, updates the dev container's base image mcr.microsoft.com/devcontainers/universal from version 2 to 5. This is a significant major version jump which introduces a high risk of breaking changes to the development environment. Such a large update can affect the underlying operating system, pre-installed tools, and language runtimes, potentially causing dependency conflicts or build failures. My review highlights this risk to ensure the development environment remains stable after the update.

[gemini-code-assist]

Updating the dev container image from version 2 to 5 is a major upgrade that introduces a high risk of breaking the development environment. Major version changes in the devcontainers/universal image often involve OS upgrades (e.g., from Debian 11 to 12) and changes to pre-installed software versions. This can lead to dependency conflicts with packages in requirements.txt or other runtime errors, potentially blocking development workflows.