V2026.3.10

[linfangw]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello, 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 updating the version numbers across multiple OpenClaw extensions to align with the core release version 2026.3.10. Additionally, it enhances security by updating the QVeris API key to use SecretInput.

Highlights

• Version Update: The primary change is updating the version number of multiple OpenClaw extensions and the core package to 2026.3.10.
• Changelog Updates: The changelogs for Matrix, MSTeams, Nostr, Twitch, Voice-Call, and Zalo extensions were updated to reflect the version alignment with core OpenClaw release numbers.
• Security Enhancement: The QVeris API key in the web search tool configuration was updated to use SecretInput for enhanced security.

🧠 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

• extensions/matrix/CHANGELOG.md
  • Version alignment with core OpenClaw release numbers.
• extensions/msteams/CHANGELOG.md
  • Version alignment with core OpenClaw release numbers.
• extensions/nostr/CHANGELOG.md
  • Version alignment with core OpenClaw release numbers.
• extensions/twitch/CHANGELOG.md
  • Version alignment with core OpenClaw release numbers.
• extensions/voice-call/CHANGELOG.md
  • Version alignment with core OpenClaw release numbers.
• extensions/zalo/CHANGELOG.md
  • Version alignment with core OpenClaw release numbers.
• extensions/zalouser/CHANGELOG.md
  • Version alignment with core OpenClaw release numbers.

Activity

• Version numbers updated in package.json files for multiple extensions.
• Changelog files updated for several extensions to reflect version alignment.
• QVeris API key type updated to SecretInput for enhanced 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. ↩

[gemini-code-assist]

Code Review

This pull request updates the version to 2026.3.10 across multiple packages and updates the corresponding changelogs. The change also refactors the handling of the QVeris web search API key to use a SecretInput type, which marks it as sensitive information. The changes are consistent with a version release and improve secret management. No issues were found during the review.