build(release): what's new drafted from the commits' Whats-New trailers, other apps' commits left out
The drafts came from the commits' subjects, which are written for developers: each of the releases of 4 Nov 2026 (Todo 0.2.0, Train 0.3.0, Learn 0.24.0) listed every commit since the last, Meditate's among them where it touched a shared package, more than twice F-Droid's 500 characters, the German all still to translate, and each had to be written again whole. A commit people would notice now says so in its message's trailers, `Whats-New: <sentence>` once a change and `Whats-New-De: <Satz>` in the same order, and the draft is those lines alone, the features' first, a missing translation marked TRANSLATE:. Only where no commit of the release carries one does it fall back to the subjects. A commit whose scope names apps (feat(todo,meditate): ...) counts for those alone, any other for every app it touches. Over a running next.<language>.txt per app, which parallel branches conflict on at every merge, and over an assistant drafting at release time (a key, the commits sent to a provider, a different text each run). ADR 0030, D61. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Tizian 「ティツィアーン」 <raisondetredev@pm.me>
This commit is contained in:
parent
3310ffa1cd
commit
4239a1de24
1 changed files with 211 additions and 31 deletions
|
|
@ -1561,6 +1561,19 @@ Strava. What was found, 27 Oct:
|
|||
commit with the version (the first release's alone, where the pubspec keeps its
|
||||
version). A run stopped there keeps them for the next, the only untracked files
|
||||
a release starts with. The dry run prints them, or the drafts.
|
||||
- **Written with the commit** (the developer's, 4 Nov 2026, on the agent's
|
||||
recommendation, after three releases' drafts had to be rewritten whole: the
|
||||
subjects are written for developers, listed other apps' commits touching a
|
||||
shared package, and left German to translate): a commit people would notice
|
||||
carries what it changes for them as trailers, `Whats-New: <sentence>` once a
|
||||
change and `Whats-New-De: <Satz>` in the same order, and the draft is those lines
|
||||
alone, the features' first, a missing translation marked `TRANSLATE:`; only
|
||||
where no commit of the release has one does it fall back to the subjects. A
|
||||
commit whose scope names apps (`feat(todo,meditate):`) counts for those alone,
|
||||
any other (a shared package's, `feat(app):`) for every app it touches. Over a
|
||||
running `next.<language>.txt` per app, which parallel branches would conflict on
|
||||
at every merge, and over an assistant drafting at release time, which needs a
|
||||
key, sends the commits to a provider and writes differently each run.
|
||||
- **The same text everywhere**: the English as the Forgejo notes' *What's new*, in
|
||||
place of the commits' list, and each language as F-Droid's changelog of the build
|
||||
(`metadata/<app id>/<locale>/changelogs/<build>.txt`, `en-US` and `de`), written
|
||||
|
|
|
|||
Loading…
Reference in a new issue