@wirecat/cli-base 0.55.0 → 0.55.1

package/CHANGELOG.md

@@ -8,6 +8,21 @@ Versions before 0.8.0 are in the [git tags](https://github.com/WireCatLabs/cli-b
 Every entry says what changed as a caller sees it, why, and what to watch for — the rules are
 [`docs/dev/CONVENTIONS.md`](docs/dev/CONVENTIONS.md#the-changelog).
 
+## 0.55.1 — 25.10.2026
+
+### Fixed
+
+- **`WC-ARCH-21` names the call that exists** ([Architecture](docs/standards/architecture.md)): a CLI registers its provider with `store.accounts.registerProvider(entry)`. The rule named a `registerProvider` import from `@wirecat/cli-core/store`, which cli-core 0.421.0 does not export.
+
+- **`cli-dev changelog restore` no longer stops a release when the newest tag has no section of its own**
+  ([releases standard](docs/standards/releases.md#wc-rel-15--fold-a-late-pending-section-into-the-unpublished-version-before-publishing)).
+  A raise that renamed the previous section instead of dating `## Unreleased` leaves a tag whose changelog has no
+  `## <version> — ` heading, and the command threw on every later `bin/release`. Nothing was released under that
+  heading, so there is nothing to restore: the command now prints why on stderr and changes nothing.
+  `restoreReleased` from `@wirecat/cli-base/release` returns `undefined` in that case instead of throwing; a
+  changelog with no section for the tagged version still throws. A CLI that skipped the restore for this case can
+  drop the skip and pin this version.
+
 ## 0.55.0 — 25.10.2026
 
 ### Added

package/dist/dev/main.js

@@ -10,6 +10,7 @@ import { parseArgs } from "node:util";
 import spawn from "cross-spawn";
 import * as v from "valibot";
 import { parseCommandsDocument } from "../commands/document.js";
+import { taggedSection } from "../release/fold.js";
 import { changelogProblems, docsProblems, JOURNAL_IDS, markdownFiles, packageVersion, structureProblems, versionScript, } from "../release/index.js";
 import { AUDIT_BLOCKS, defineParityGroups, PARITY_GROUPS, REQUIRED_ROOTS } from "../standards/audit.js";
 import { defineReasons } from "../standards/errors.js";
@@ -123,6 +124,10 @@ const changelog = (args, io) => {
         if (action === "restore") {
             const shell = processShell(io.cwd);
             const tag = newestTag(shell, relative(io.cwd, file));
+            if (!taggedSection(tag.text, tag.version)) {
+                io.err(`v${tag.version}'s changelog has no section of its own; nothing to restore`);
+                return 0;
+            }
             const change = (text) => restoreChange(text, tag.text, tag.version, values.unreleased);
             if (values.land) {
                 const landed = landChange({

package/dist/release/fold.d.ts

@@ -13,12 +13,15 @@ export declare const foldUnreleased: (text: string, version: string, unreleased?
  * when no heading repeats there. The caller makes sure the version is not on npm.
  */
 export declare const mergeRepeatedHeadings: (text: string, version: string) => string | undefined;
+/** The `## <version> — ` section of a changelog, or `undefined` when it has none. */
+export declare const taggedSection: (text: string, version: string) => string | undefined;
 /**
  * Puts the section of `version`, the newest tagged one, back to its text in that tag. A pull request
  * checked before the version was dated or tagged and merged after it adds its entry there with no
  * guard to see it, though that code ships only in the next version: each such entry moves to the unreleased
  * section, after its entries under the same `###` heading. `undefined` when the section matches the tag the
- * way the changelog guard compares them.
+ * way the changelog guard compares them, or when the tag's changelog has no section for `version`: nothing was
+ * released under that heading, so there is nothing to restore.
  */
 export declare const restoreReleased: (text: string, tagText: string, version: string, unreleased?: string) => {
     text: string;

package/dist/release/fold.js

@@ -85,18 +85,21 @@ const entries = (section) => [...section.headings].flatMap(([heading, lines]) =>
     }
     return found;
 });
+/** The `## <version> — ` section of a changelog, or `undefined` when it has none. */
+export const taggedSection = (text, version) => text.split(/\n(?=## )/).find((block) => block.startsWith(`## ${version} — `));
 /**
  * Puts the section of `version`, the newest tagged one, back to its text in that tag. A pull request
  * checked before the version was dated or tagged and merged after it adds its entry there with no
  * guard to see it, though that code ships only in the next version: each such entry moves to the unreleased
  * section, after its entries under the same `###` heading. `undefined` when the section matches the tag the
- * way the changelog guard compares them.
+ * way the changelog guard compares them, or when the tag's changelog has no section for `version`: nothing was
+ * released under that heading, so there is nothing to restore.
  */
 export const restoreReleased = (text, tagText, version, unreleased = "Unreleased") => {
     const dated = (block) => block.startsWith(`## ${version} — `);
-    const tagged = tagText.split(/\n(?=## )/).find(dated);
+    const tagged = taggedSection(tagText, version);
     if (!tagged)
-        throw new Error(`the v${version} tag's changelog has no "## ${version} — " section`);
+        return undefined;
     const blocks = text.split(/\n(?=## )/);
     const index = blocks.findIndex(dated);
     if (index < 0)

package/docs/standards/architecture.md

@@ -206,8 +206,8 @@ at start-up and the `serve` relay are in [Lifecycle](lifecycle.md); the store's
 
 ### WC-ARCH-21 · A CLI registers its provider in the store; an unknown provider's rows are skipped, never guessed
 
-Every run, a CLI writes its provider's entry — `{ name, kind, aliases, command }` — with `registerProvider` from
-`@wirecat/cli-core/store`. cli-core reads its built-in providers plus the stored entries when the store opens, so
+Every run, a CLI writes its provider's entry — `{ name, kind, aliases, command }` — with
+`store.accounts.registerProvider(entry)` on the store from `openStore()` (`@wirecat/cli-core/store`). cli-core reads its built-in providers plus the stored entries when the store opens, so
 every other CLI knows the new provider's kind without a cli-core release. A row whose provider no entry names is left
 out of search and listed under `skipped`, with the hint to run that CLI once.
 

package/docs/standards/releases.md

@@ -173,7 +173,9 @@ on the [CI](ci.md) page.
   section, through a pull request. Then, while npm does not have the version, `bin/release` runs
   `cli-dev changelog fold --land --version <x.y.z>`. It folds the pending section into the dated one, and merges any
   repeated `###` heading, through a pull request.
-- **Exceptions:** only the newest tag is compared; an older section that differs from its tag stays as it is.
+- **Exceptions:** only the newest tag is compared; an older section that differs from its tag stays as it is. A
+  newest tag whose changelog has no section of its own has nothing to restore: the command says so and changes
+  nothing.
 - **Applies to:** all CLIs and shared libraries. **Since:** cli-base 0.41.0. **Rulings:** none.
 
 ### WC-REL-16 · The package ships only the files it names

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wirecat/cli-base",
-  "version": "0.55.0",
+  "version": "0.55.1",
   "description": "The parts every command line tool needs: output modes, terminal rendering, error model, exit codes, credentials, clocks",
   "license": "Apache-2.0",
   "author": "Viacheslav Ptsarev",