Release Policy

Release notes are stored at /updates and tracked by version with feature, improvement, and fix entries.

The goal of the release policy is to make product changes easy to scan before you rely on a workflow, share a tool internally, or update linked documentation.

How to read

1. Check version and date on each card
2. Use highlights for quick scanning
3. Inspect the detailed markdown body for impact scope

Version policy

• Semantic versioning style for major/minor/patch
• Korean and English copy is synchronized per release
• Documentation and updates pages use consistent language

Documentation expectations

• User-facing changes should be reflected in docs or release notes when behavior materially changes.
• Copy and terminology should stay aligned across supported locales as updates roll out.
• The updates page should remain the source of truth for shipped product changes.

Last updated: 2026-03-14