whats-new drafts from player-facing notes first (whatsNew.source, docs/RELEASE-<version>.md, the CHANGELOG section of the version or Unreleased; --release, --from-git) and only then from the git log; internal jargon warnings (SDK / vendor names, developer and version-control words, file paths, issue ids, code identifiers) with plain alternatives in the draft and whats-new check, one list in cli/lib/jargon.ts, whatsNew.allowWords keeps a word; skill: write from what players feel, never from commit messages; tests
This commit is contained in:
parent
e9507d8884
commit
bab3f63227
9 changed files with 287 additions and 21 deletions
10
CHANGELOG.md
10
CHANGELOG.md
|
|
@ -1,5 +1,15 @@
|
|||
# Changelog
|
||||
|
||||
## Unreleased
|
||||
|
||||
- **`whats-new` drafts from player-facing notes before the git log.** It takes `whatsNew.source`, then
|
||||
`docs/RELEASE-<version>.md`, then the CHANGELOG.md section of the version (else Unreleased); version from
|
||||
`--release`, else package.json. Only without one (or with `--from-git`) it drafts from commit messages, and says so.
|
||||
- **Internal jargon warnings in release notes.** The draft and `whats-new check` name SDK / vendor names, developer
|
||||
and version-control words, file paths, issue ids and code identifiers, each with a plain alternative; warnings never
|
||||
block. One list in cli/lib/jargon.ts; `whatsNew.allowWords` keeps a word. The whats-new skill says to write from what
|
||||
players feel, never from commit messages.
|
||||
|
||||
## 0.8.3 · 2026-10-14
|
||||
|
||||
Docs: no private account names in the published package. `npx storebound` prompts work on Node again (the [Y/n]
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue