tools: command records, Distribution and versioning group - one line per cause, examples, prohibitions (#142)
Files changed: - CHANGES.md - VERSION - tools/CONTRACT.md - tools/chemenu/commands/dist_cmd.py - tools/chemenu/commands/version_cmd.py
This commit is contained in:
1 parent
df8ff2fa22
commit
9d6ca6b193
5 files changed
+710
-265
No files matched your search
+19
-1
@@ -59,7 +59,7 @@ concern - readable here, never shipped as something to parse.
|
||||
|
||||
---
|
||||
|
||||
## 7.1.0-beta.8 - 2026-09-26 - Command records, Catalog and log group: bullets, examples, prohibitions
|
||||
## 7.1.0-beta.9 - 2026-09-26 - Command records, Distribution and versioning group: one line per cause, examples, prohibitions
|
||||
|
||||
**Author:** Torben Nehmer
|
||||
|
||||
@@ -77,6 +77,7 @@ concern - readable here, never shipped as something to parse.
|
||||
- wikitool: usage lines name wikitool, and the -h acceptance checks become tests
|
||||
- Command records, Git group: NOTES as bullets, one exit line per cause, examples and prohibitions
|
||||
- Command records, Catalog and log group: bullets, examples, prohibitions
|
||||
- Command records, Distribution and versioning group: one line per cause, examples, prohibitions
|
||||
<!-- /wikitool:bumps -->
|
||||
|
||||
### CalDAV task-tracker provider (Nextcloud Tasks, iOS Reminders); review reports unknown-value findings instead of skipping them
|
||||
@@ -206,6 +207,23 @@ prose: check the tail of `kb/log.md` before re-running after an uncertain outcom
|
||||
the command already did. `log status` no longer claims it "reports 0" for a missing log - it
|
||||
reports that nothing is logged yet, which is what it always printed.
|
||||
|
||||
### Command records, Distribution and versioning group: one line per cause, examples, prohibitions
|
||||
|
||||
`dist export`, `dist upgrade` and the six `version` commands rewritten the same way; text only.
|
||||
The long single-paragraph records - `dist upgrade` and `version bump` above all - are now one
|
||||
bullet per behaviour, and each exit-1 cause carries its own reaction, taken from what the
|
||||
command's own error message already tells the caller (`migrate baseline`, `migrate status`,
|
||||
commit or stash, `upstream merge`). Three corrections to what the records claimed: `dist upgrade`
|
||||
listed an equal source version both as a no-op success and as an exit-1 refusal - it is a
|
||||
success, and EXIT STATUS now says so; `dist export` and `dist upgrade` gained the exit-1 causes
|
||||
their code already had but their records omitted (a missing licence, an export plan leaking
|
||||
instance data, a bad archive checksum); and `version regrade`'s NOTES, garbled when they were
|
||||
moved over mechanically, read as sentences again. Two code comments changed with them: the one
|
||||
above `dist export`'s `raw/`/`incoming/` anchors had claimed `.gitignore` drops `incoming/`,
|
||||
which stopped being true when `!/incoming/.gitkeep` was added, and `dist upgrade`'s stamp write
|
||||
now carries the reasoning for writing the stamp whole after `--keep-local`, which used to live
|
||||
in the record.
|
||||
|
||||
---
|
||||
|
||||
## 7.0.0 - 2026-09-22 - Task-Tracker-Anbindung: Vorhaben als Seitenart, Verpflichtungsschicht, Weekly Review als Read-Time-Join
|
||||
|
||||
Reference in new issue
Block a user