update-grpc
Procedure to update gRPC, Netty, and BoringSSL versions in this Java/Maven project while maintaining compatibility
Works with
---
name: update-grpc
description: Procedure to update gRPC, Netty, and BoringSSL versions in this Java/Maven project while maintaining compatibility
license: Apache-2.0
---
gRPC, Netty, and BoringSSL are tightly coupled together. Incompatible version combinations will cause runtime failures. When updating gRPC, you **must** follow this procedure:
1. Browse the compatibility matrix at https://github.com/grpc/grpc-java/blob/master/SECURITY.md#netty to determine the correct Netty and BoringSSL (netty-tcnative-boringssl-static) versions for the target gRPC version.
2. Update the version properties in **all** of the following POM files:
- `pom.xml` (root)
- `central/pom.xml`
- `agent/shaded/core/pom.xml`
- `agent/shaded/central-https-linux/pom.xml`
- `agent/shaded/central-https-windows/pom.xml`
- `agent/shaded/central-https-osx/pom.xml`
3. All three versions (gRPC, Netty, BoringSSL) must be updated **together** — never update one without checking the others.
4. After modifying the POM files, grep the project for any other references to the old versions to ensure nothing was missed:
```
grep -r "OLD_GRPC_VERSION" --include="pom.xml"
grep -r "OLD_NETTY_VERSION" --include="pom.xml"
grep -r "OLD_BORINGSSL_VERSION" --include="pom.xml"
```More API Design skills
lark-event
larksuite/cli
Lark/Feishu real-time event listening / subscribing / consuming: stream events as NDJSON via `lark-cli event consume <EventKey>` (covers IM messages/reactions/chat changes, Approval status changes, Task updates, VC meeting started/joined/ended, Minutes generated, Whiteboard updated, etc.). Use for Lark bots, real-time message processing, long-running subscribers, streaming webhook/push handlers. Supports `--max-events` / `--timeout` bounded runs and a stderr ready-marker contract — designed for AI agents running as subprocesses.
lark-contact
larksuite/cli
飞书 / Lark 通讯录:按姓名 / 邮箱解析成 open_id,或按 open_id 反查姓名 / 部门 / 邮箱 / 联系方式 / 个人状态 / 签名,以及按关键词搜索当前用户可见的机器人 / 智能体(agent)。当用户提到一个名字要下一步发消息 / 排日程,或拿到 open_id 想查具体信息时使用。不负责部门树遍历、按部门列员工、组织架构图,这类需求走原生 OpenAPI。
lark-openapi-explorer
larksuite/cli
飞书/Lark 原生 OpenAPI 探索:从官方文档库中挖掘未经 CLI 封装的原生 OpenAPI 接口。当用户的需求无法被现有 lark-* skill 或 lark-cli 已注册命令满足,需要查找并调用原生飞书 OpenAPI 时使用。

