Skip to content

docs(contracts): define api change rules - #16

Open
Hqzdev wants to merge 1 commit into
mainfrom
docs/api-contract-change-rules
Open

docs(contracts): define api change rules#16
Hqzdev wants to merge 1 commit into
mainfrom
docs/api-contract-change-rules

Conversation

@Hqzdev

@Hqzdev Hqzdev commented Jun 6, 2026

Copy link
Copy Markdown
Owner

Что сделано

Обновлен docs/architecture/API_CONTRACTS.md: описаны contract sources, что считается contract change, compatibility policy, response checklist и error contract.

Зачем

API contracts нужны web, bot и сервисным consumer-ам. Явные правила изменения снижают риск случайного breaking change без coordinated deploy.

Что проверено

  • git diff --check

Риски и ограничения

Docs-only изменение. Contract tests и OpenAPI validation не запускались, потому что spec не менялся.

The API contract guide needed explicit compatibility and error-shape
rules. Documenting the change checklist reduces accidental breaking
changes across web, bot and service consumers.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@vercel

vercel Bot commented Jun 6, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
metrix Ready Ready Preview, Comment Jun 6, 2026 9:37am

@Hqzdev Hqzdev added documentation Improvements or additions to documentation contracts API contracts and compatibility checks api API packages and contracts labels Jun 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api API packages and contracts contracts API contracts and compatibility checks documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants