@forumulate/cli 0.22.4 → 0.22.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -3,6 +3,53 @@
3
3
  Releases of `@forumulate/cli`. Earlier versions are described in the git history of
4
4
  `packages/cli` (`release(cli): …` commits).
5
5
 
6
+ ## 0.22.5
7
+
8
+ ### Changed
9
+ - This file now covers 0.22.0 to 0.22.4. Those releases shipped without their entries here. No code changes.
10
+
11
+ ## 0.22.4
12
+
13
+ ### Fixed
14
+ - `plan`/`apply --skip consent` (with a space) dropped the `consent` block. Before, the CLI read `consent` as the manifest path; only `--skip=consent` worked. `--host` and `--app-routes` had the same bug and are fixed too.
15
+ - A `forumulate.yaml` monitor whose declared `kind` differs from the stored one now plans with a warning: a kind cannot change in place, so apply deletes the monitor and makes it again as the new kind, and its uptime history (and a heartbeat's ping URL) start over. It used to plan `update`, report applied and stay the old kind. This is decided by the API, so it holds for every CLI version.
16
+
17
+ ## 0.22.3
18
+
19
+ ### Added
20
+ - `forumulate routes list --host <host>` prints the paths we answer on a host you share with your own app (what the edge routes by). `routes check --host <host> --app-routes <file>` exits 1 when one of your app's routes is one of them or sits under one. Next.js folder names are understood. A dynamic segment that only shadows a mount is a warning.
21
+ - `${NAME:-fallback}` in `forumulate.yaml`. `${NAME:-}` makes a variable optional.
22
+ - `plan`/`apply --skip consent,pages,…` drops top-level blocks before their variables are read. A skipped block is reported as skipped and is never pruned.
23
+
24
+ ### Changed
25
+ - `dir:` is relative to the manifest's folder, not the directory you run from. This was always the behavior; the apply guide now says so.
26
+
27
+ ## 0.22.2
28
+
29
+ ### Fixed
30
+ - `publish` checks each page `icon` against the page icon set (`GET /icons?for=page`). The dry run warns with `file:line`. A real run still sets the page's other metadata and names the file whose icon was refused. Before, one bad icon stopped the whole publish with a 422 that named no file, and the dry run planned it as normal. A page the server refuses no longer stops the pages after it.
31
+ - The dead-link check knows your site's mounts. A link to another space's root on the same site (`/docs`, `/community/`) is no longer reported dead.
32
+ - The missing-description warning quotes the description the live page actually serves. It used to say the tagline is used, which was wrong.
33
+
34
+ ### Also from this date (API, any CLI version)
35
+ - `spaces[].settings.publishPings` in `forumulate.yaml`, on every space type: the same body as `PUT …/publish-pings`, so IndexNow is declared in one place for docs, blog, legal and the rest. `settings.careers.indexing` still works. The manifest is validated by the API, so this needs no CLI upgrade; 0.22.2 and later ship the SDK types for it.
36
+
37
+ ## 0.22.1
38
+
39
+ ### Changed
40
+ - `apply --env-out`: with two or more heartbeats, the bare `FORUMULATE_PING_ENDPOINT` / `FORUMULATE_PING_TOKEN` lines are removed from the file. Which heartbeat they meant would otherwise depend on the order things were created. The per-monitor `FORUMULATE_PING_ENDPOINT_<NAME>` / `FORUMULATE_PING_TOKEN_<NAME>` lines stay.
41
+ - `plan`'s warning on a heartbeat that still takes `GET` names the date GET pings end: 2027-03-01.
42
+ - Help links to the monitors guide point at `/guides/monitors` (the old address redirects).
43
+
44
+ ## 0.22.0
45
+
46
+ ### Added
47
+ - `apply --env-out <file>` writes every heartbeat's ping endpoint and token as dotenv lines (`FORUMULATE_PING_ENDPOINT_<NAME>`, `FORUMULATE_PING_TOKEN_<NAME>`, plus the bare names when there is exactly one heartbeat). Lines that aren't ours are kept, so it can be your app's own `.env`. The file is written with mode 0600.
48
+ - `plan` warns on a heartbeat that still accepts `GET` pings.
49
+
50
+ ### Changed
51
+ - `plan` prints an unchanged step when it carries a warning, so the warning is not hidden.
52
+
6
53
  ## 0.21.0
7
54
 
8
55
  ### Changed
package/dist/version.d.ts CHANGED
@@ -4,5 +4,5 @@
4
4
  * Its own module so `api list` can name the CLI that bundled its operation
5
5
  * list without importing `run.ts` (which imports it).
6
6
  */
7
- export declare const VERSION = "0.22.4";
7
+ export declare const VERSION = "0.22.5";
8
8
  //# sourceMappingURL=version.d.ts.map
package/dist/version.js CHANGED
@@ -7,5 +7,5 @@ exports.VERSION = void 0;
7
7
  * Its own module so `api list` can name the CLI that bundled its operation
8
8
  * list without importing `run.ts` (which imports it).
9
9
  */
10
- exports.VERSION = '0.22.4';
10
+ exports.VERSION = '0.22.5';
11
11
  //# sourceMappingURL=version.js.map
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@forumulate/cli",
3
- "version": "0.22.4",
3
+ "version": "0.22.5",
4
4
  "description": "Command-line interface for Forumulate — manage orgs, spaces, docs, and search from your terminal.",
5
5
  "license": "MIT",
6
6
  "homepage": "https://forumulate.com/guides",