api-changelog-versioning
>
Works with
--- name: api-changelog-versioning description: > license: MIT --- # API Changelog & Versioning ## Table of Contents - [Overview](#overview) - [When to Use](#when-to-use) - [Quick Start](#quick-start) - [Reference Guides](#reference-guides) - [Best Practices](#best-practices) ## Overview Create comprehensive API changelogs that document changes, deprecations, breaking changes, and provide migration guides for API consumers. ## When to Use - API version changelogs - Breaking changes documentation - Migration guides between versions - Deprecation notices - API upgrade guides - Backward compatibility notes - Version comparison ## Quick Start - Version comparison ````markdown # API Changelog ## Version 3.0.0 - 2025-01-15 ### 🚨 Breaking Changes #### Authentication Method Changed **Previous (v2):** ```http GET /api/users Authorization: Token abc123 ``` ## Reference Guides Detailed implementations in the `references/` directory: | Guide | Contents | |---|---| | [🚨 Breaking Changes](references/breaking-changes.md) | 🚨 Breaking Changes | | [✨ New Features](references/new-features.md) | ✨ New Features | | [🔧 Improvements](references/improvements.md) | 🔧 Improvements | | [🔒 Security](references/security.md) | 🔒 Security, 🗑️ Deprecated, 📊 Version Support Policy | | [Step 1: Update Base URL](references/step-1-update-base-url.md) | Step 1: Update Base URL, Step 2: Migrate Authentication, Step 3: Update Response Parsing, Step 4: Update Error Handling (+2 more) | ## Best Practices ### ✅ DO - Clearly mark breaking changes - Provide migration guides with code examples - Include before/after comparisons - Document deprecation timelines - Show impact on existing implementations - Provide SDKs for major versions - Use semantic versioning - Give advance notice (3-6 months) - Maintain backward compatibility when possible - Document version support policy ### ❌ DON'T - Make breaking changes without notice - Remove endpoints without deprecation period - Skip migration examples - Forget to version your API - Change behavior without documentation - Rush deprecations
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 时使用。

