From 787c97698b11c85151fd3cd1c5a196f16423f70f Mon Sep 17 00:00:00 2001 From: leemour Date: Wed, 18 Nov 2026 15:24:08 +0100 Subject: [PATCH] chore: release 0.700.0 bin/release: 0.699.0 is already on npm. Only the number changes: package.json, the CHANGELOG heading, and the changes/ fragments collected under it. --- CHANGELOG.md | 37 ++++++++++++++++++++++++++++ changes/feat-html-markdown.md | 8 ------ changes/feat-manifest-attio-deals.md | 16 ------------ changes/feat-permission-values.md | 14 ----------- package.json | 2 +- 5 files changed, 38 insertions(+), 39 deletions(-) delete mode 100644 changes/feat-html-markdown.md delete mode 100644 changes/feat-manifest-attio-deals.md delete mode 100644 changes/feat-permission-values.md diff --git a/CHANGELOG.md b/CHANGELOG.md index 1d6542749..dde0e33a4 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -5,6 +5,43 @@ Notable changes to `@wirecat/cli-core` (`@wirecat/cli-messaging` up to 0.261.0, minor version may break callers, and says how under "Changed — may break callers". `pnpm docs:check` checks the shape of this file. +## 0.700.0 — 18.11.2026 + +### Added + +- **`htmlToMarkdown` and `markdownToHtml` in `@wirecat/cli-core/documents`**, for the content category: a blog keeps + HTML (WordPress, Ghost), and a CLI shows and takes Markdown. WordPress block comments and Ghost card comments go, + and so do scripts, styles, frames, event attributes, raw HTML from Markdown, and links and images whose scheme is + not http(s), mailto or tel: a post body is untrusted. Tested on one post as WordPress 6.9 stores and renders it and + as Ghost 6.78 renders it; Markdown that went through HTML once comes back the same. The converters are unified's + `hast-util-from-html`, `hast-util-to-mdast`, `mdast-util-to-hast` and `hast-util-to-html`, loaded on first use. +- **A CRM source from a manifest reads a pipeline answered as a flat list of stages** (`stages.each: "."`, grouped by + `stages.pipeline` or one pipeline), and a hook `pipelines..outcome` decides a stage's outcome the data cannot + say. Attio's deal stages and Pipedrive's `/stages` answer this way. +- **`custom.typed` reads the account's own fields from typed entries with their history**, as Attio keeps them: the + current entry's value by its type (`TYPED_VALUE_PATHS`, overridable), a multiple field or several current entries as a list. + `fields.keep` takes `{ path, is }`, so a config file can say which fields are the account's own. +- **`entities.person.search` and `entities.organization.search` give a manifest source a live `list`**, for `people + list` and `organizations list`: words through the search call's `"{query}"`, none through `list`. A condition it + cannot send is refused, not dropped; a live list pages by offset, so a cursor-paged search is refused. +- `hooks.extend` gets the service's `call` as its second argument. +- **The `api` group checks a key by a field's value, as WordPress publishes by `status: "publish"`.** A manifest + permission with `values` (cli-base's `permissions.valueKeys`) applies when the call's JSON body or its query holds + one of those values: `{ key: "posts.publish", values: { status: ["publish", "future"] } }` asks for + `posts.publish` before `api post-wp-v2-posts --body '{"status":"publish"}'` and lets a draft through. Both places + count, because WordPress reads the same parameter from either. So a profile that denies publishing also stops an + agent that publishes through the raw `api` group. `--dry-run` and discovery show the key with + `with status publish or future`. + +### Changed — may break callers + +- **cli-core needs `@wirecat/cli-base` 0.118.0**, which carries the manifest's `values` and WordPress's + `wpJsonToOpenApi`. A CLI that pins an older cli-base raises it with this cli-core. + +### Fixed + +- `crmManifestFake` matches a call whatever page size and offset the source asked for, a live list setting its own, and writes a stage's won or lost flag as a boolean or a word, as its schema takes it. + ## 0.699.0 — 18.11.2026 ### Added diff --git a/changes/feat-html-markdown.md b/changes/feat-html-markdown.md deleted file mode 100644 index db6821158..000000000 --- a/changes/feat-html-markdown.md +++ /dev/null @@ -1,8 +0,0 @@ -### Added - -- **`htmlToMarkdown` and `markdownToHtml` in `@wirecat/cli-core/documents`**, for the content category: a blog keeps - HTML (WordPress, Ghost), and a CLI shows and takes Markdown. WordPress block comments and Ghost card comments go, - and so do scripts, styles, frames, event attributes, raw HTML from Markdown, and links and images whose scheme is - not http(s), mailto or tel: a post body is untrusted. Tested on one post as WordPress 6.9 stores and renders it and - as Ghost 6.78 renders it; Markdown that went through HTML once comes back the same. The converters are unified's - `hast-util-from-html`, `hast-util-to-mdast`, `mdast-util-to-hast` and `hast-util-to-html`, loaded on first use. diff --git a/changes/feat-manifest-attio-deals.md b/changes/feat-manifest-attio-deals.md deleted file mode 100644 index c9dd405b2..000000000 --- a/changes/feat-manifest-attio-deals.md +++ /dev/null @@ -1,16 +0,0 @@ -### Added - -- **A CRM source from a manifest reads a pipeline answered as a flat list of stages** (`stages.each: "."`, grouped by - `stages.pipeline` or one pipeline), and a hook `pipelines..outcome` decides a stage's outcome the data cannot - say. Attio's deal stages and Pipedrive's `/stages` answer this way. -- **`custom.typed` reads the account's own fields from typed entries with their history**, as Attio keeps them: the - current entry's value by its type (`TYPED_VALUE_PATHS`, overridable), a multiple field or several current entries as a list. - `fields.keep` takes `{ path, is }`, so a config file can say which fields are the account's own. -- **`entities.person.search` and `entities.organization.search` give a manifest source a live `list`**, for `people - list` and `organizations list`: words through the search call's `"{query}"`, none through `list`. A condition it - cannot send is refused, not dropped; a live list pages by offset, so a cursor-paged search is refused. -- `hooks.extend` gets the service's `call` as its second argument. - -### Fixed - -- `crmManifestFake` matches a call whatever page size and offset the source asked for, a live list setting its own, and writes a stage's won or lost flag as a boolean or a word, as its schema takes it. diff --git a/changes/feat-permission-values.md b/changes/feat-permission-values.md deleted file mode 100644 index c82fd8d13..000000000 --- a/changes/feat-permission-values.md +++ /dev/null @@ -1,14 +0,0 @@ -### Added - -- **The `api` group checks a key by a field's value, as WordPress publishes by `status: "publish"`.** A manifest - permission with `values` (cli-base's `permissions.valueKeys`) applies when the call's JSON body or its query holds - one of those values: `{ key: "posts.publish", values: { status: ["publish", "future"] } }` asks for - `posts.publish` before `api post-wp-v2-posts --body '{"status":"publish"}'` and lets a draft through. Both places - count, because WordPress reads the same parameter from either. So a profile that denies publishing also stops an - agent that publishes through the raw `api` group. `--dry-run` and discovery show the key with - `with status publish or future`. - -### Changed — may break callers - -- **cli-core needs `@wirecat/cli-base` 0.118.0**, which carries the manifest's `values` and WordPress's - `wpJsonToOpenApi`. A CLI that pins an older cli-base raises it with this cli-core. diff --git a/package.json b/package.json index 17ee4936c..bfd8a978e 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "@wirecat/cli-core", - "version": "0.699.0", + "version": "0.700.0", "description": "The messenger-neutral half of a messaging CLI: domain model, message locators, rendering, name resolution, the SQLite seam, the command skeleton and shared read commands, the send guard, run records and the message store", "license": "Apache-2.0", "author": "Viacheslav Ptsarev",