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 mcr.microsoft.com/devcontainers/universal Docker image used in the development container configuration. This is a major version bump, ensuring the project utilizes the latest features and improvements provided by the updated base image for a more consistent and up-to-date development environment.

Highlights

• Dependency Update: Updated the mcr.microsoft.com/devcontainers/universal Docker image tag from v2 to v5 in the devcontainer configuration.

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

Changelog

• .devcontainer/devcontainer.json
  • Updated the image property to use version 5 of the mcr.microsoft.com/devcontainers/universal Docker image.

Activity

• Pull request automatically generated by Renovate bot.
• Automerge is disabled, requiring manual merge.

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 updates the mcr.microsoft.com/devcontainers/universal Docker image from version 2 to 5. This is a significant major version update which carries a risk of introducing breaking changes to the development environment. I have added a review comment to highlight this risk and recommend thorough testing before merging.

[gemini-code-assist]

A major version update from 2 to 5 for the dev container image carries a high risk of introducing breaking changes. This could include updates to the underlying OS, changes in pre-installed tool versions, or removal of packages, potentially disrupting the development workflow. It is highly recommended to build and test the dev container environment thoroughly to validate its functionality before merging this change.