fix(registry): bump telegram channel version for capabilities change

[zmanian]

Summary

• Bumps telegram channel version 0.2.2 -> 0.2.3 to match the validation_endpoint addition in telegram.capabilities.json
• Unblocks staging promotion PR chore: promote staging to main (2026-03-12 11:12 UTC) #1032 which fails the version-check CI gate

Test plan

• CI version-check passes
• Staging promote chore: promote staging to main (2026-03-12 11:12 UTC) #1032 can be re-run after merge

Generated with Claude Code

[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 updates the version of the Telegram channel within its registry configuration. This essential change ensures compatibility with new capabilities and resolves a critical CI failure that was blocking a significant staging promotion, allowing for smoother deployment processes.

Highlights

• Telegram Channel Version Update: The Telegram channel version was incremented from 0.2.2 to 0.2.3 to align with the recent addition of a validation_endpoint in telegram.capabilities.json.
• Unblocking Staging Promotion: This version bump resolves a version-check CI gate failure, which was preventing staging promotion PR chore: promote staging to main (2026-03-12 11:12 UTC) #1032 from proceeding.

Changelog

• registry/channels/telegram.json
  • Updated the version field from 0.2.2 to 0.2.3.
  • Modified the url for the wasm32-wasip2 artifact to reflect the new 0.2.3 version.

Activity

• The CI version-check is expected to pass with this change.
• Staging promotion PR chore: promote staging to main (2026-03-12 11:12 UTC) #1032 can be re-run and is expected to succeed after this 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 bumps the version of the Telegram channel in the registry. However, there is a critical issue: the sha256 hash for the artifact has not been updated to match the new version, which will break downloads. Additionally, there's a version mismatch between this registry file and the capabilities file in the source tree, which could cause confusion.

[gemini-code-assist]

The artifact URL has been updated to point to version 0.2.3, but the sha256 hash on the next line has not been updated. This will cause integrity checks to fail when downloading the new artifact. Please update the sha256 hash to match the new telegram-0.2.3-wasm32-wasip2.tar.gz artifact.

[gemini-code-assist]

The channel version is being bumped to 0.2.3, but the corresponding capabilities file at channels-src/telegram/telegram.capabilities.json still shows version 0.2.2. To maintain consistency, it's recommended to also update the version in the capabilities file. This helps avoid confusion about which version of the capabilities corresponds to this registry entry.

[G7CNF]

CI context: this PR only changes \ (data/version metadata), and all style/clippy/deny checks are passing. The only failure is , which is expected for a registry JSON-only bump.\n\nCould a maintainer please add the \ label (or apply \ in commit message) to unblock merge?

[G7CNF]

CI context: this PR only changes registry/channels/telegram.json (registry data/version metadata), and style/clippy/deny checks are passing.

The only failing check is Regression test enforcement, which is expected for this JSON-only bump.

Could a maintainer please add the skip-regression-check label (or include [skip-regression-check] in commit message) to unblock merge?