Files
fullex e97480c4c9 docs(breaking-changes): introduce v2 user-impact change log
Add an internal record for v2 changes that affect how users use the
app. PR authors drop a fragment .md per change; the release manager
aggregates and translates them into the Chinese user-facing release
note at v2.0.0, then discards the fragments with v2-refactor-temp/.

Also translate v2-refactor-temp/README.md to English and link the new
directory from it.
2026-04-29 19:10:45 -07:00

679 B
Raw Permalink Blame History

title, category, severity, introduced_in_pr, date
title category severity introduced_in_pr date
<Short, user-visible headline. e.g. "Bilibili integration removed"> <removed | changed | moved | data-migration | shortcut | platform | other> <breaking | notice> <#PR number, or commit hash if no PR> <YYYY-MM-DD>

What changed

<13 sentences. Concrete user-visible behavior, not implementation.>

Why this matters to the user

<What will the user notice? When? Where?>

What the user should do

<Workaround, replacement feature, manual step, or "nothing — automatic". Mark TBD if undecided.>

Notes for release manager

<Optional. Caveats, edge cases, related entries to merge, screenshots to attach.>