From 2b280edd901fb69b2120b3e31c1f5b3ace64adb1 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Mon, 26 Oct 2026 09:23:26 +0000 Subject: [PATCH] chore(release): version packages --- .changeset/bundle-project-row.md | 5 -- .changeset/deps-issue-115.md | 10 ---- .changeset/do-sqlite-keepalive.md | 5 -- .changeset/entry-list-values-cloudflare.md | 5 -- .changeset/entry-list-values-core.md | 9 ---- .changeset/entry-list-values-mcp.md | 5 -- .changeset/entry-list-values-storage.md | 5 -- .changeset/import-plan.md | 20 -------- .changeset/render-check-escapes.md | 5 -- .changeset/restore-bundle.md | 5 -- .changeset/site-archive-export.md | 12 ----- .changeset/site-archive-import.md | 13 ------ .changeset/site-archive-replace.md | 13 ------ .changeset/studio-ended-collection-rule.md | 5 -- .changeset/testing-subpath-ships.md | 8 ---- packages/agent-runtime/CHANGELOG.md | 10 ++++ packages/agent-runtime/package.json | 2 +- packages/analytics/CHANGELOG.md | 11 +++++ packages/analytics/package.json | 2 +- packages/api/CHANGELOG.md | 25 ++++++++++ packages/api/package.json | 2 +- packages/astro-renderer/CHANGELOG.md | 19 ++++++++ packages/astro-renderer/package.json | 2 +- packages/cli/CHANGELOG.md | 54 ++++++++++++++++++++++ packages/cli/package.json | 2 +- packages/cloudflare/CHANGELOG.md | 25 ++++++++++ packages/cloudflare/package.json | 2 +- packages/comments/CHANGELOG.md | 17 +++++++ packages/comments/package.json | 2 +- packages/core-contracts/CHANGELOG.md | 4 ++ packages/core-contracts/package.json | 2 +- packages/core-ts/CHANGELOG.md | 36 +++++++++++++++ packages/core-ts/package.json | 2 +- packages/create-cloudhal/CHANGELOG.md | 11 +++++ packages/create-cloudhal/package.json | 2 +- packages/mcp-server/CHANGELOG.md | 23 +++++++++ packages/mcp-server/package.json | 2 +- packages/schedules/CHANGELOG.md | 12 +++++ packages/schedules/package.json | 2 +- packages/storage/CHANGELOG.md | 9 ++++ packages/storage/package.json | 2 +- 41 files changed, 269 insertions(+), 138 deletions(-) delete mode 100644 .changeset/bundle-project-row.md delete mode 100644 .changeset/deps-issue-115.md delete mode 100644 .changeset/do-sqlite-keepalive.md delete mode 100644 .changeset/entry-list-values-cloudflare.md delete mode 100644 .changeset/entry-list-values-core.md delete mode 100644 .changeset/entry-list-values-mcp.md delete mode 100644 .changeset/entry-list-values-storage.md delete mode 100644 .changeset/import-plan.md delete mode 100644 .changeset/render-check-escapes.md delete mode 100644 .changeset/restore-bundle.md delete mode 100644 .changeset/site-archive-export.md delete mode 100644 .changeset/site-archive-import.md delete mode 100644 .changeset/site-archive-replace.md delete mode 100644 .changeset/studio-ended-collection-rule.md delete mode 100644 .changeset/testing-subpath-ships.md diff --git a/.changeset/bundle-project-row.md b/.changeset/bundle-project-row.md deleted file mode 100644 index 4e720fc1..00000000 --- a/.changeset/bundle-project-row.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@cloudhal/core-ts": patch ---- - -`importSite` (behind `cloudhal pull`, the admin bundle route `cloudhal push` uses, and `cloudhal import`) now checks a bundle's project row before inserting it: it must be the site node's project (`projectId`), a valid Project, with its `id` and `rev` columns matching its body. Before, a bundle could plant any projects row. diff --git a/.changeset/deps-issue-115.md b/.changeset/deps-issue-115.md deleted file mode 100644 index 615673b9..00000000 --- a/.changeset/deps-issue-115.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -"@cloudhal/api": patch -"@cloudhal/cloudflare": patch -"@cloudhal/core-ts": patch -"@cloudhal/schedules": patch -"@cloudhal/astro-renderer": patch -"@cloudhal/cli": patch ---- - -Dependency patch updates (#115). `@cloudhal/api` depends on Better Auth 1.7.12 and on exactly the versions it uses itself: `@better-auth/core` and `@better-auth/api-key` 1.7.12, `@better-auth/utils` 0.5.0 and `better-call` 1.4.4. `@cloudhal/cloudflare` asks for zod ^4.6.7 (GHSA-mrhx-c7xc-m3w5 is fixed in 4.6.6). `@cloudhal/core-ts` and `@cloudhal/astro-renderer` use marked ^18.1.1. `@cloudhal/core-ts` and `@cloudhal/schedules` use temporal-polyfill 1.0.6. `@cloudhal/astro-renderer` uses vite ^8.3.5. The Studio shipped in `@cloudhal/cli` is built with React 19.3.1, TanStack Router 1.170.46 and TanStack Query 5.104.5. marked 18.1.1 splits a few unusual markdown inputs differently: a blockquote ends before an unquoted line that follows a heading, rule or HTML block, and indented HTML blocks interrupt a paragraph. A stored body like that keeps rendering and shows virtual block ids until its next write. diff --git a/.changeset/do-sqlite-keepalive.md b/.changeset/do-sqlite-keepalive.md deleted file mode 100644 index d9fd4b09..00000000 --- a/.changeset/do-sqlite-keepalive.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@cloudhal/storage": patch ---- - -createMiniflareDoSqlite() sends its Durable Object calls over kept-alive connections instead of opening a new TCP connection per call through Miniflare 4's dispatchFetch, so long suites no longer exhaust local ports on macOS (#116). diff --git a/.changeset/entry-list-values-cloudflare.md b/.changeset/entry-list-values-cloudflare.md deleted file mode 100644 index e1a92559..00000000 --- a/.changeset/entry-list-values-cloudflare.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@cloudhal/cloudflare": patch ---- - -The admin Worker's minute tick gains a `lists.backfill` system job (every five minutes): a budgeted `rebuildListValues` for listed collections that are new, changed, reset by a race or older than migration 0029, sized to the tick plan. Its declared cost (16 statements on the free plan, 150 on paid) is the run's statement budget, which the backfill enforces on every statement, discovery included, and each run starts at another waiting collection. On the paid plan it also removes rows of collections that list no fields any more, never those of a collection listed while it ran. diff --git a/.changeset/entry-list-values-core.md b/.changeset/entry-list-values-core.md deleted file mode 100644 index 7626a8b4..00000000 --- a/.changeset/entry-list-values-core.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -"@cloudhal/core-ts": patch ---- - -RFC-0042 §4, #110: `queryContentEntries` (the API's `GET /entries?where=…`, Studio's lists, MCP `list_entries`) answers `where`, `orderBy`, status, locale, `limit` and `offset` in SQL from the new `entry_list_values` side table once a collection is ready, instead of reading and evaluating the whole collection; results are the shared evaluator's, which stays the fallback (term filters, collections not ready, operands SQL cannot compare exactly) and the oracle of a seeded property suite on SQLite, D1 and Durable Object SQLite. On the 10,000-entry benchmark the store path drops from 124 ms CPU / 10,001 rows (SQLite) and 176 ms / 10,003 rows read (D1) to 0.6 ms / 22 rows and 5.3 ms / 5,068 rows read; a page at offset 4,980 costs about the same as the first. - -The store keeps the table exact. Entry creates, updates, moves and deletes write an entry's rows (its `listFields` values as `resolveFields` reads them) in their own batch, and an original's write rewrites its same-site translations' rows; site writes and field operations that change a collection's list definitions reset its readiness in the same batch, and imports reset the site's. A race never refuses a write: it marks the collection not ready. New `rebuildListValues(sql, options)` is the resumable, budgeted backfill (guarded per chunk, safe to run concurrently; `budget.statements` bounds every statement it issues, `start` rotates where a run begins, `tidy` removes rows of unlisted collections); `updateSite`, finished field operations and `importSite` run it for what they reset, and `openLocalStore` runs it on open. A field operation's revert resets every listed collection whose values its restored bodies change. `deleteContentEntry` behaves as before. - -`revertTagsToTerms` now leaves an entry that was edited after the migration's before-snapshot (by a concurrent write, or before a resumed run) as it is and reports it in `edited`, instead of restoring its earlier fields, status or collection. diff --git a/.changeset/entry-list-values-mcp.md b/.changeset/entry-list-values-mcp.md deleted file mode 100644 index c72e3750..00000000 --- a/.changeset/entry-list-values-mcp.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@cloudhal/mcp-server": patch ---- - -`list_entries` with `orderBy` and `limit` lets the store page (in SQL once the collection's list values are ready, RFC-0042 §4, #110) instead of loading every match. Arguments, cursors and output are unchanged; without `orderBy` the list keeps its last-updated order. diff --git a/.changeset/entry-list-values-storage.md b/.changeset/entry-list-values-storage.md deleted file mode 100644 index 65b703fb..00000000 --- a/.changeset/entry-list-values-storage.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@cloudhal/storage": patch ---- - -Migration `0029_entry_list_values` (RFC-0042 §4, #110): `entry_list_values`, the indexed list-field values of entries (field, presence, number, text, collection-sort key, creation time, node, locale and status) with a query index and a per-node index, and `entry_list_state`, each listed collection's readiness (definition fingerprint, ready flag, backfill epoch and cursor). DDL only; existing data is untouched. diff --git a/.changeset/import-plan.md b/.changeset/import-plan.md deleted file mode 100644 index 7d7f3db1..00000000 --- a/.changeset/import-plan.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -"@cloudhal/core-ts": patch ---- - -`importSite`, used by `cloudhal pull`, by the admin bundle route `cloudhal push` uses, and by `cloudhal import`, now runs every check before it writes anything, the bootstrap conflict and the 1000-statement limit included, and plans the media ledger with them. A refused bundle leaves the target as it was; before, node bodies could land ahead of a conflict and snapshots ahead of the size limit. Only a storage failure can stop it between its writes, and importing the bundle again completes it. New checks, each before the first write: - -- Every node body the target lacks must be a valid contract document of the kind of each snapshot ref that points to it, with that ref's id and rev, of the bundle's site (precompiled validators). A body no snapshot references is refused. Before, a body was only checked against its hash, so a crafted bundle could put invalid content behind the published snapshot. -- Node and snapshot ids may not belong to another site of the target, each appears once, and no two nodes share a kind and key or a translation group and locale (the node batch's unique keys). -- Every takedown entry has its fields with their types (`reason`, `legal`, `by`, `at`). -- The media ledger (`snapshot_blobs`) reads the target's own asset bodies, never the bundle's text for a body the target already holds. - -New `planImport(to, bundle, options)` returns what an import would change, without writing: - -- the nodes added, changed and removed; -- the snapshots and node bodies to add; -- whether the project row is new; -- the listed media that are present, missing, of another size or taken down on the target; -- the bundle's takedowns, those whose bytes the target holds (an import deletes them) and those its ledger does not hold yet. - -With `report: true` it returns a bootstrap conflict and missing media instead of throwing them. A node body that is not JSON is refused as `blob is not JSON` instead of with the parser's message. diff --git a/.changeset/render-check-escapes.md b/.changeset/render-check-escapes.md deleted file mode 100644 index ba44e2a3..00000000 --- a/.changeset/render-check-escapes.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@cloudhal/mcp-server": patch ---- - -render_page's long-line and input-label checks handle whitespace correctly again. A plain template literal ate the backslash, so the in-page script received `/s/` and `/s+/` instead of `/\s/` and `/\s+/`. As a result, long-line counted the letter "s" as blank and every real space and indentation run as text. input-label split `aria-labelledby` on the letter "s" and reported labelled inputs as unlabelled. The check parts are now `String.raw` templates. diff --git a/.changeset/restore-bundle.md b/.changeset/restore-bundle.md deleted file mode 100644 index 28b4b028..00000000 --- a/.changeset/restore-bundle.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@cloudhal/core-ts": patch ---- - -New `restoreBundle(from, snapshot)`: a site bundle of one snapshot's nodes, rebuilt from the stored node bodies, for `importSite(…, { mode: "replace" })`, which checks it like any bundle. The site's working copy and published pointer become that snapshot's again (`cloudhal import --revert`, RFC-0039). Revs only move forward: a node the site holds at the snapshot's rev or a later one, with other content, comes back at the rev after its current one, so a Studio tab or agent still holding a rev that node had gets a conflict instead of saving over it; a node whose content already is the snapshot's is left as it is. It lists the media those nodes need and carries the store's takedowns among them, so taken-down content stays down; a missing node body, or one that is not the node its snapshot ref names, is refused before anything is written. `exportSite`'s output is unchanged. diff --git a/.changeset/site-archive-export.md b/.changeset/site-archive-export.md deleted file mode 100644 index 97b67529..00000000 --- a/.changeset/site-archive-export.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -"@cloudhal/cli": patch ---- - -New `cloudhal export` (RFC-0039, #47) writes one site of the local project to a single `.cloudhal` file. The file is a gzipped tar holding the site's content graph (nodes, snapshots and the node bodies they reference, as NDJSON parts), its media files and its takedown ledger, with every file's SHA-256 listed in the manifest. The flags: - -- `--out ` names the file, and replaces a file already there once the new one is complete. By default the file is `-.cloudhal` in the current folder, dated by the newest timestamp among the rows it holds (deleting content alone does not move that date; the next edit or snapshot does). A file already at the default name is replaced only by the same archive; any other (a later edit the same day, other flags, a deletion) is left alone and the export asks for `--out`. -- `--site ` exports another site listed in `cloudhal.json` `sites`. `--site`, `--no-media` and `--latest-only` are refused on every other command. -- `--no-media` writes the graph only. -- `--latest-only` keeps only the published and the latest snapshot, and only the media they and the current content need. It is refused while a field operation is unfinished (`cloudhal fields continue|revert`). - -A damaged or missing local media file stops the export (run `cloudhal media verify`); so do Ctrl-C and SIGTERM. Either way no file is written and an existing one is left as it was. Exporting an unchanged site again with the same CLI and Node version gives the same bytes. An archive never contains user accounts, sessions, roles, agent keys, comments, readers, analytics, the audit log, scheduled releases, automations, schedule runs, pending approvals, open edit suggestions, deployment secrets or webhook credentials, and the export prints this list. Its history does name who made each change (the user or agent of each snapshot, upload, block edit, review and takedown). diff --git a/.changeset/site-archive-import.md b/.changeset/site-archive-import.md deleted file mode 100644 index b9f058a1..00000000 --- a/.changeset/site-archive-import.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -"@cloudhal/cli": patch ---- - -New `cloudhal import [--dry-run]` (RFC-0039, #47) reads a `.cloudhal` file written by `cloudhal export` into the local project, keeping the site's id. - -- It reads the file twice. First it verifies every file's size and SHA-256, every row and every node body (each must be the node its snapshot refs name), and checks the archive against the project. A damaged or edited file, invalid content, an archive of another site, a site whose nodes differ, or missing media is therefore refused before anything is written. Then it reads the file again, refusing it if it changed in between, copies the media the project lacks and imports the graph, keeping the archive's published snapshot as `cloudhal pull` does. -- By default a bootstrap import. The archive's site must be `cloudhal.json`'s `siteId` or listed in `sites`, and the project must not hold it yet or hold exactly its nodes; missing snapshots, node bodies and media are added. A site whose nodes differ is refused; `--replace` replaces them (see its own note). -- An archive written with `--no-media` imports only when the project already has its media. -- Taken-down content stays down: the archive's takedowns are recorded and their bytes never written, a local copy of content the archive's ledger took down is deleted (the summary says how many), and an archive carrying content this project has taken down is refused. -- `--dry-run` prints the manifest and what the import would add, change or remove (nodes by kind and title, snapshots, media to copy), writes nothing, and exits 1 when the import would be refused. -- Ctrl-C and SIGTERM stop the import before the graph is written; media already copied stay in the blob store, unreferenced, and the next import reuses them. A storage failure while the graph is written says the import stopped partway; running it again completes it, search index included. -- Opening an existing local store applies pending migrations, as every command does; a project without one gets none from a dry run or a refused import. diff --git a/.changeset/site-archive-replace.md b/.changeset/site-archive-replace.md deleted file mode 100644 index 0e9231bb..00000000 --- a/.changeset/site-archive-replace.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -"@cloudhal/cli": patch ---- - -`cloudhal import --replace [--dry-run]` (RFC-0039 rollout step 4, #47) makes the local site's nodes the archive's, its published snapshot included, as `cloudhal pull --replace` does. `cloudhal push` still keeps a deployment's own published snapshot, so a local replace never moves production. Snapshots are only ever added. - -- When it changes a site the project already holds, the current graph is saved first as a snapshot labelled `before import ` and the result as `import `; the summary prints `(undo: cloudhal import --revert )`. A new or unchanged site gets no snapshot; a site the plan found unchanged is checked again just before the write, and refused if another process changed it meanwhile. A run that stopped after the first snapshot reuses it the next time. -- The archive's nodes keep their revs, as with `pull --replace`. A Studio tab or agent still holding a node at the rev the archive gives it can save over it without a conflict, so the summary counts those nodes and says to reload open Studio tabs. -- New `cloudhal import --revert [--dry-run]` brings the site back to a `before import` snapshot, its published snapshot included, saving the current graph first as `before revert import `, so a revert can itself be reverted. Its revs only move forward: a node edited since comes back at the rev after its current one, so a stale editor gets a conflict. Studio's rollback only moves the published pointer to an earlier snapshot, which cannot undo a replace. -- An archive of a site `cloudhal.json` does not list switches its `siteId`, and the old id's place in `sites`, to the archive's, editing only those values in the file (layout and other keys stay as written), once the import has landed. The old site stays in the local store, unlisted and untouched; writing the old id back by hand undoes the switch (`--revert` restores nodes only), and the summary names `cloudhal site delete` to remove the old site for good. A deployed project is warned that its deployment serves the old site, and that a deployment of the imported site is updated from the project that deployed it. -- Refused before anything is written: open releases of the site (cancel them in Studio), an unfinished field operation, a hostname another local site serves (now a refusal `--dry-run` reports, for bootstrap imports too), and an archive site id `cloudhal.json` cannot name. -- `--dry-run` shows the snapshots it would take, the published-snapshot change and the `cloudhal.json` change; it exits 0, or 1 when the import would be refused. -- `--cancel-schedules` is now refused by every command but `cloudhal push`. diff --git a/.changeset/studio-ended-collection-rule.md b/.changeset/studio-ended-collection-rule.md deleted file mode 100644 index edf9995b..00000000 --- a/.changeset/studio-ended-collection-rule.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@cloudhal/cli": patch ---- - -Studio shows **Ended (collection rule)** beside the status of a published entry whose collection's expiry has passed (RFC-0042 §3.3, #113), in the collection list and in the entry editor's header. Until now such an entry looked plainly published while the site had already left it out of lists, or answered "not found". The badge explains itself on hover, from the keyboard and with a tap on touch screens. It names the date field, when the entry ended in the site's time zone, and what the site does: the page keeps its address but leaves lists, feeds, the sitemap and search, or the page answers "not found". Drafts, embargoed entries and entries whose own "Hide after" has passed get no badge (their own dates show in the editor's Schedule card). A translation reads its original's date only while the original is published, as the site does. The badge and its words load only for collections that have an expiry. Translations of the new words are AI drafts awaiting review. diff --git a/.changeset/testing-subpath-ships.md b/.changeset/testing-subpath-ships.md deleted file mode 100644 index dfadd45f..00000000 --- a/.changeset/testing-subpath-ships.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -"@cloudhal/storage": patch -"@cloudhal/analytics": patch -"@cloudhal/comments": patch -"@cloudhal/schedules": patch ---- - -The `./testing` subpath now ships. The published packages pointed `./testing` at `dist/src/testing.js` and `.d.ts`, but the build left those files out, so importing `@cloudhal/{storage,analytics,comments,schedules}/testing` failed with ERR_MODULE_NOT_FOUND. The suites run on your own vitest, 3 or later, which is an optional peer dependency. `@cloudhal/storage`'s Miniflare helpers also load your own `miniflare`, an optional peer of any version. The ranges are wide on purpose. When a direct dependency's optional peer does not match the copy in your project, npm stops with ERESOLVE, even if nothing imports `./testing`. No semver range matches the prerelease miniflare that wrangler currently brings in, so with a narrower range npm would install a second miniflare beside it. diff --git a/packages/agent-runtime/CHANGELOG.md b/packages/agent-runtime/CHANGELOG.md index 334cee1d..ca429ef2 100644 --- a/packages/agent-runtime/CHANGELOG.md +++ b/packages/agent-runtime/CHANGELOG.md @@ -1,5 +1,15 @@ # @cloudhal/agent-runtime +## 0.6.2 + +### Patch Changes + +- Updated dependencies [970c8a1] +- Updated dependencies [6cb7945] +- Updated dependencies [8a30e30] + - @cloudhal/storage@0.6.2 + - @cloudhal/core-contracts@0.6.2 + ## 0.6.1 ### Patch Changes diff --git a/packages/agent-runtime/package.json b/packages/agent-runtime/package.json index 5adfb24c..93b239ea 100644 --- a/packages/agent-runtime/package.json +++ b/packages/agent-runtime/package.json @@ -1,6 +1,6 @@ { "name": "@cloudhal/agent-runtime", - "version": "0.6.1", + "version": "0.6.2", "description": "Cloudhal agent runtime: policy engine (actors, scopes, approvals), skill loader, audit log", "license": "Apache-2.0", "homepage": "https://cloudhal.dev", diff --git a/packages/analytics/CHANGELOG.md b/packages/analytics/CHANGELOG.md index 5570526e..a9f49fa5 100644 --- a/packages/analytics/CHANGELOG.md +++ b/packages/analytics/CHANGELOG.md @@ -1,5 +1,16 @@ # @cloudhal/analytics +## 0.6.2 + +### Patch Changes + +- 8a30e30: The `./testing` subpath now ships. The published packages pointed `./testing` at `dist/src/testing.js` and `.d.ts`, but the build left those files out, so importing `@cloudhal/{storage,analytics,comments,schedules}/testing` failed with ERR_MODULE_NOT_FOUND. The suites run on your own vitest, 3 or later, which is an optional peer dependency. `@cloudhal/storage`'s Miniflare helpers also load your own `miniflare`, an optional peer of any version. The ranges are wide on purpose. When a direct dependency's optional peer does not match the copy in your project, npm stops with ERESOLVE, even if nothing imports `./testing`. No semver range matches the prerelease miniflare that wrangler currently brings in, so with a narrower range npm would install a second miniflare beside it. +- Updated dependencies [970c8a1] +- Updated dependencies [6cb7945] +- Updated dependencies [8a30e30] + - @cloudhal/storage@0.6.2 + - @cloudhal/core-contracts@0.6.2 + ## 0.6.1 ### Patch Changes diff --git a/packages/analytics/package.json b/packages/analytics/package.json index 960001e6..0cb59b3d 100644 --- a/packages/analytics/package.json +++ b/packages/analytics/package.json @@ -1,6 +1,6 @@ { "name": "@cloudhal/analytics", - "version": "0.6.1", + "version": "0.6.2", "description": "Cloudhal site analytics (RFC-0006): query model, classifiers, beacon handler, SQLite/D1 store, daily rollups and Workers Analytics Engine adapters. Worker-safe.", "license": "Apache-2.0", "homepage": "https://cloudhal.dev", diff --git a/packages/api/CHANGELOG.md b/packages/api/CHANGELOG.md index d24d0f42..0a886f4f 100644 --- a/packages/api/CHANGELOG.md +++ b/packages/api/CHANGELOG.md @@ -1,5 +1,30 @@ # @cloudhal/api +## 0.6.2 + +### Patch Changes + +- d91ef8f: Dependency patch updates (#115). `@cloudhal/api` depends on Better Auth 1.7.12 and on exactly the versions it uses itself: `@better-auth/core` and `@better-auth/api-key` 1.7.12, `@better-auth/utils` 0.5.0 and `better-call` 1.4.4. `@cloudhal/cloudflare` asks for zod ^4.6.7 (GHSA-mrhx-c7xc-m3w5 is fixed in 4.6.6). `@cloudhal/core-ts` and `@cloudhal/astro-renderer` use marked ^18.1.1. `@cloudhal/core-ts` and `@cloudhal/schedules` use temporal-polyfill 1.0.6. `@cloudhal/astro-renderer` uses vite ^8.3.5. The Studio shipped in `@cloudhal/cli` is built with React 19.3.1, TanStack Router 1.170.46 and TanStack Query 5.104.5. marked 18.1.1 splits a few unusual markdown inputs differently: a blockquote ends before an unquoted line that follows a heading, rule or HTML block, and indented HTML blocks interrupt a paragraph. A stored body like that keeps rendering and shows virtual block ids until its next write. +- Updated dependencies [7223152] +- Updated dependencies [d91ef8f] +- Updated dependencies [970c8a1] +- Updated dependencies [f73d05a] +- Updated dependencies [f73d05a] +- Updated dependencies [6cb7945] +- Updated dependencies [f669266] +- Updated dependencies [77fa9e5] +- Updated dependencies [786a455] +- Updated dependencies [8a30e30] + - @cloudhal/core-ts@0.6.2 + - @cloudhal/schedules@0.6.2 + - @cloudhal/astro-renderer@0.6.2 + - @cloudhal/storage@0.6.2 + - @cloudhal/mcp-server@0.6.2 + - @cloudhal/analytics@0.6.2 + - @cloudhal/comments@0.6.2 + - @cloudhal/agent-runtime@0.6.2 + - @cloudhal/core-contracts@0.6.2 + ## 0.6.1 ### Patch Changes diff --git a/packages/api/package.json b/packages/api/package.json index fc37eac8..b86fdcb3 100644 --- a/packages/api/package.json +++ b/packages/api/package.json @@ -1,6 +1,6 @@ { "name": "@cloudhal/api", - "version": "0.6.1", + "version": "0.6.2", "description": "Cloudhal HTTP API (Hono): sites, pages, entries, snapshots, auth — runs on Node and Cloudflare Workers", "license": "Apache-2.0", "homepage": "https://cloudhal.dev", diff --git a/packages/astro-renderer/CHANGELOG.md b/packages/astro-renderer/CHANGELOG.md index e0639473..3f0a36ee 100644 --- a/packages/astro-renderer/CHANGELOG.md +++ b/packages/astro-renderer/CHANGELOG.md @@ -1,5 +1,24 @@ # @cloudhal/astro-renderer +## 0.6.2 + +### Patch Changes + +- d91ef8f: Dependency patch updates (#115). `@cloudhal/api` depends on Better Auth 1.7.12 and on exactly the versions it uses itself: `@better-auth/core` and `@better-auth/api-key` 1.7.12, `@better-auth/utils` 0.5.0 and `better-call` 1.4.4. `@cloudhal/cloudflare` asks for zod ^4.6.7 (GHSA-mrhx-c7xc-m3w5 is fixed in 4.6.6). `@cloudhal/core-ts` and `@cloudhal/astro-renderer` use marked ^18.1.1. `@cloudhal/core-ts` and `@cloudhal/schedules` use temporal-polyfill 1.0.6. `@cloudhal/astro-renderer` uses vite ^8.3.5. The Studio shipped in `@cloudhal/cli` is built with React 19.3.1, TanStack Router 1.170.46 and TanStack Query 5.104.5. marked 18.1.1 splits a few unusual markdown inputs differently: a blockquote ends before an unquoted line that follows a heading, rule or HTML block, and indented HTML blocks interrupt a paragraph. A stored body like that keeps rendering and shows virtual block ids until its next write. +- Updated dependencies [7223152] +- Updated dependencies [d91ef8f] +- Updated dependencies [970c8a1] +- Updated dependencies [f73d05a] +- Updated dependencies [6cb7945] +- Updated dependencies [f669266] +- Updated dependencies [786a455] +- Updated dependencies [8a30e30] + - @cloudhal/core-ts@0.6.2 + - @cloudhal/storage@0.6.2 + - @cloudhal/analytics@0.6.2 + - @cloudhal/comments@0.6.2 + - @cloudhal/core-contracts@0.6.2 + ## 0.6.1 ### Patch Changes diff --git a/packages/astro-renderer/package.json b/packages/astro-renderer/package.json index 9243a646..66e88c94 100644 --- a/packages/astro-renderer/package.json +++ b/packages/astro-renderer/package.json @@ -1,6 +1,6 @@ { "name": "@cloudhal/astro-renderer", - "version": "0.6.1", + "version": "0.6.2", "description": "Render a Cloudhal Site Graph with Astro: data sources (live/snapshot), section components and the cloudhal() integration", "license": "Apache-2.0", "homepage": "https://cloudhal.dev", diff --git a/packages/cli/CHANGELOG.md b/packages/cli/CHANGELOG.md index cfc52ec2..8759c0b7 100644 --- a/packages/cli/CHANGELOG.md +++ b/packages/cli/CHANGELOG.md @@ -1,5 +1,59 @@ # @cloudhal/cli +## 0.6.2 + +### Patch Changes + +- d91ef8f: Dependency patch updates (#115). `@cloudhal/api` depends on Better Auth 1.7.12 and on exactly the versions it uses itself: `@better-auth/core` and `@better-auth/api-key` 1.7.12, `@better-auth/utils` 0.5.0 and `better-call` 1.4.4. `@cloudhal/cloudflare` asks for zod ^4.6.7 (GHSA-mrhx-c7xc-m3w5 is fixed in 4.6.6). `@cloudhal/core-ts` and `@cloudhal/astro-renderer` use marked ^18.1.1. `@cloudhal/core-ts` and `@cloudhal/schedules` use temporal-polyfill 1.0.6. `@cloudhal/astro-renderer` uses vite ^8.3.5. The Studio shipped in `@cloudhal/cli` is built with React 19.3.1, TanStack Router 1.170.46 and TanStack Query 5.104.5. marked 18.1.1 splits a few unusual markdown inputs differently: a blockquote ends before an unquoted line that follows a heading, rule or HTML block, and indented HTML blocks interrupt a paragraph. A stored body like that keeps rendering and shows virtual block ids until its next write. +- 330b650: New `cloudhal export` (RFC-0039, #47) writes one site of the local project to a single `.cloudhal` file. The file is a gzipped tar holding the site's content graph (nodes, snapshots and the node bodies they reference, as NDJSON parts), its media files and its takedown ledger, with every file's SHA-256 listed in the manifest. The flags: + + - `--out ` names the file, and replaces a file already there once the new one is complete. By default the file is `-.cloudhal` in the current folder, dated by the newest timestamp among the rows it holds (deleting content alone does not move that date; the next edit or snapshot does). A file already at the default name is replaced only by the same archive; any other (a later edit the same day, other flags, a deletion) is left alone and the export asks for `--out`. + - `--site ` exports another site listed in `cloudhal.json` `sites`. `--site`, `--no-media` and `--latest-only` are refused on every other command. + - `--no-media` writes the graph only. + - `--latest-only` keeps only the published and the latest snapshot, and only the media they and the current content need. It is refused while a field operation is unfinished (`cloudhal fields continue|revert`). + + A damaged or missing local media file stops the export (run `cloudhal media verify`); so do Ctrl-C and SIGTERM. Either way no file is written and an existing one is left as it was. Exporting an unchanged site again with the same CLI and Node version gives the same bytes. An archive never contains user accounts, sessions, roles, agent keys, comments, readers, analytics, the audit log, scheduled releases, automations, schedule runs, pending approvals, open edit suggestions, deployment secrets or webhook credentials, and the export prints this list. Its history does name who made each change (the user or agent of each snapshot, upload, block edit, review and takedown). +- 2c18a7c: New `cloudhal import [--dry-run]` (RFC-0039, #47) reads a `.cloudhal` file written by `cloudhal export` into the local project, keeping the site's id. + + - It reads the file twice. First it verifies every file's size and SHA-256, every row and every node body (each must be the node its snapshot refs name), and checks the archive against the project. A damaged or edited file, invalid content, an archive of another site, a site whose nodes differ, or missing media is therefore refused before anything is written. Then it reads the file again, refusing it if it changed in between, copies the media the project lacks and imports the graph, keeping the archive's published snapshot as `cloudhal pull` does. + - By default a bootstrap import. The archive's site must be `cloudhal.json`'s `siteId` or listed in `sites`, and the project must not hold it yet or hold exactly its nodes; missing snapshots, node bodies and media are added. A site whose nodes differ is refused; `--replace` replaces them (see its own note). + - An archive written with `--no-media` imports only when the project already has its media. + - Taken-down content stays down: the archive's takedowns are recorded and their bytes never written, a local copy of content the archive's ledger took down is deleted (the summary says how many), and an archive carrying content this project has taken down is refused. + - `--dry-run` prints the manifest and what the import would add, change or remove (nodes by kind and title, snapshots, media to copy), writes nothing, and exits 1 when the import would be refused. + - Ctrl-C and SIGTERM stop the import before the graph is written; media already copied stay in the blob store, unreferenced, and the next import reuses them. A storage failure while the graph is written says the import stopped partway; running it again completes it, search index included. + - Opening an existing local store applies pending migrations, as every command does; a project without one gets none from a dry run or a refused import. +- 33ae911: `cloudhal import --replace [--dry-run]` (RFC-0039 rollout step 4, #47) makes the local site's nodes the archive's, its published snapshot included, as `cloudhal pull --replace` does. `cloudhal push` still keeps a deployment's own published snapshot, so a local replace never moves production. Snapshots are only ever added. + + - When it changes a site the project already holds, the current graph is saved first as a snapshot labelled `before import ` and the result as `import `; the summary prints `(undo: cloudhal import --revert )`. A new or unchanged site gets no snapshot; a site the plan found unchanged is checked again just before the write, and refused if another process changed it meanwhile. A run that stopped after the first snapshot reuses it the next time. + - The archive's nodes keep their revs, as with `pull --replace`. A Studio tab or agent still holding a node at the rev the archive gives it can save over it without a conflict, so the summary counts those nodes and says to reload open Studio tabs. + - New `cloudhal import --revert [--dry-run]` brings the site back to a `before import` snapshot, its published snapshot included, saving the current graph first as `before revert import `, so a revert can itself be reverted. Its revs only move forward: a node edited since comes back at the rev after its current one, so a stale editor gets a conflict. Studio's rollback only moves the published pointer to an earlier snapshot, which cannot undo a replace. + - An archive of a site `cloudhal.json` does not list switches its `siteId`, and the old id's place in `sites`, to the archive's, editing only those values in the file (layout and other keys stay as written), once the import has landed. The old site stays in the local store, unlisted and untouched; writing the old id back by hand undoes the switch (`--revert` restores nodes only), and the summary names `cloudhal site delete` to remove the old site for good. A deployed project is warned that its deployment serves the old site, and that a deployment of the imported site is updated from the project that deployed it. + - Refused before anything is written: open releases of the site (cancel them in Studio), an unfinished field operation, a hostname another local site serves (now a refusal `--dry-run` reports, for bootstrap imports too), and an archive site id `cloudhal.json` cannot name. + - `--dry-run` shows the snapshots it would take, the published-snapshot change and the `cloudhal.json` change; it exits 0, or 1 when the import would be refused. + - `--cancel-schedules` is now refused by every command but `cloudhal push`. +- 68cd5a1: Studio shows **Ended (collection rule)** beside the status of a published entry whose collection's expiry has passed (RFC-0042 §3.3, #113), in the collection list and in the entry editor's header. Until now such an entry looked plainly published while the site had already left it out of lists, or answered "not found". The badge explains itself on hover, from the keyboard and with a tap on touch screens. It names the date field, when the entry ended in the site's time zone, and what the site does: the page keeps its address but leaves lists, feeds, the sitemap and search, or the page answers "not found". Drafts, embargoed entries and entries whose own "Hide after" has passed get no badge (their own dates show in the editor's Schedule card). A translation reads its original's date only while the original is published, as the site does. The badge and its words load only for collections that have an expiry. Translations of the new words are AI drafts awaiting review. +- Updated dependencies [7223152] +- Updated dependencies [d91ef8f] +- Updated dependencies [970c8a1] +- Updated dependencies [df8695e] +- Updated dependencies [f73d05a] +- Updated dependencies [f73d05a] +- Updated dependencies [6cb7945] +- Updated dependencies [f669266] +- Updated dependencies [77fa9e5] +- Updated dependencies [786a455] +- Updated dependencies [8a30e30] + - @cloudhal/core-ts@0.6.2 + - @cloudhal/api@0.6.2 + - @cloudhal/cloudflare@0.6.2 + - @cloudhal/schedules@0.6.2 + - @cloudhal/storage@0.6.2 + - @cloudhal/mcp-server@0.6.2 + - @cloudhal/analytics@0.6.2 + - @cloudhal/comments@0.6.2 + - @cloudhal/agent-runtime@0.6.2 + - @cloudhal/core-contracts@0.6.2 + ## 0.6.1 ### Patch Changes diff --git a/packages/cli/package.json b/packages/cli/package.json index ccc96281..ba3c740d 100644 --- a/packages/cli/package.json +++ b/packages/cli/package.json @@ -1,6 +1,6 @@ { "name": "@cloudhal/cli", - "version": "0.6.1", + "version": "0.6.2", "description": "cloudhal — create, run and build Cloudhal sites locally", "license": "Apache-2.0", "homepage": "https://cloudhal.dev", diff --git a/packages/cloudflare/CHANGELOG.md b/packages/cloudflare/CHANGELOG.md index 30076a61..e30d4c19 100644 --- a/packages/cloudflare/CHANGELOG.md +++ b/packages/cloudflare/CHANGELOG.md @@ -1,5 +1,30 @@ # @cloudhal/cloudflare +## 0.6.2 + +### Patch Changes + +- d91ef8f: Dependency patch updates (#115). `@cloudhal/api` depends on Better Auth 1.7.12 and on exactly the versions it uses itself: `@better-auth/core` and `@better-auth/api-key` 1.7.12, `@better-auth/utils` 0.5.0 and `better-call` 1.4.4. `@cloudhal/cloudflare` asks for zod ^4.6.7 (GHSA-mrhx-c7xc-m3w5 is fixed in 4.6.6). `@cloudhal/core-ts` and `@cloudhal/astro-renderer` use marked ^18.1.1. `@cloudhal/core-ts` and `@cloudhal/schedules` use temporal-polyfill 1.0.6. `@cloudhal/astro-renderer` uses vite ^8.3.5. The Studio shipped in `@cloudhal/cli` is built with React 19.3.1, TanStack Router 1.170.46 and TanStack Query 5.104.5. marked 18.1.1 splits a few unusual markdown inputs differently: a blockquote ends before an unquoted line that follows a heading, rule or HTML block, and indented HTML blocks interrupt a paragraph. A stored body like that keeps rendering and shows virtual block ids until its next write. +- df8695e: The admin Worker's minute tick gains a `lists.backfill` system job (every five minutes): a budgeted `rebuildListValues` for listed collections that are new, changed, reset by a race or older than migration 0029, sized to the tick plan. Its declared cost (16 statements on the free plan, 150 on paid) is the run's statement budget, which the backfill enforces on every statement, discovery included, and each run starts at another waiting collection. On the paid plan it also removes rows of collections that list no fields any more, never those of a collection listed while it ran. +- Updated dependencies [7223152] +- Updated dependencies [d91ef8f] +- Updated dependencies [970c8a1] +- Updated dependencies [f73d05a] +- Updated dependencies [f73d05a] +- Updated dependencies [6cb7945] +- Updated dependencies [f669266] +- Updated dependencies [77fa9e5] +- Updated dependencies [786a455] +- Updated dependencies [8a30e30] + - @cloudhal/core-ts@0.6.2 + - @cloudhal/api@0.6.2 + - @cloudhal/schedules@0.6.2 + - @cloudhal/storage@0.6.2 + - @cloudhal/mcp-server@0.6.2 + - @cloudhal/analytics@0.6.2 + - @cloudhal/comments@0.6.2 + - @cloudhal/agent-runtime@0.6.2 + ## 0.6.1 ### Patch Changes diff --git a/packages/cloudflare/package.json b/packages/cloudflare/package.json index 5fab1076..be1b4040 100644 --- a/packages/cloudflare/package.json +++ b/packages/cloudflare/package.json @@ -1,6 +1,6 @@ { "name": "@cloudhal/cloudflare", - "version": "0.6.1", + "version": "0.6.2", "description": "Cloudhal on Cloudflare: the admin Worker (API, auth, MCP, Studio) over D1 + R2", "license": "Apache-2.0", "homepage": "https://cloudhal.dev", diff --git a/packages/comments/CHANGELOG.md b/packages/comments/CHANGELOG.md index 02675360..3dd11baf 100644 --- a/packages/comments/CHANGELOG.md +++ b/packages/comments/CHANGELOG.md @@ -1,5 +1,22 @@ # @cloudhal/comments +## 0.6.2 + +### Patch Changes + +- 8a30e30: The `./testing` subpath now ships. The published packages pointed `./testing` at `dist/src/testing.js` and `.d.ts`, but the build left those files out, so importing `@cloudhal/{storage,analytics,comments,schedules}/testing` failed with ERR_MODULE_NOT_FOUND. The suites run on your own vitest, 3 or later, which is an optional peer dependency. `@cloudhal/storage`'s Miniflare helpers also load your own `miniflare`, an optional peer of any version. The ranges are wide on purpose. When a direct dependency's optional peer does not match the copy in your project, npm stops with ERESOLVE, even if nothing imports `./testing`. No semver range matches the prerelease miniflare that wrangler currently brings in, so with a narrower range npm would install a second miniflare beside it. +- Updated dependencies [7223152] +- Updated dependencies [d91ef8f] +- Updated dependencies [970c8a1] +- Updated dependencies [f73d05a] +- Updated dependencies [6cb7945] +- Updated dependencies [f669266] +- Updated dependencies [786a455] +- Updated dependencies [8a30e30] + - @cloudhal/core-ts@0.6.2 + - @cloudhal/storage@0.6.2 + - @cloudhal/core-contracts@0.6.2 + ## 0.6.1 ### Patch Changes diff --git a/packages/comments/package.json b/packages/comments/package.json index 6d9174c8..5c02ea9b 100644 --- a/packages/comments/package.json +++ b/packages/comments/package.json @@ -1,6 +1,6 @@ { "name": "@cloudhal/comments", - "version": "0.6.1", + "version": "0.6.2", "description": "Cloudhal reader comments (RFC-0007): settings and thread state, text normalising and content rules, linkify, first-party proof of work, the submission pipeline, purge planner, retention plan and the SQLite/D1 store. Worker-safe.", "license": "Apache-2.0", "homepage": "https://cloudhal.dev", diff --git a/packages/core-contracts/CHANGELOG.md b/packages/core-contracts/CHANGELOG.md index a7d320d7..f5999443 100644 --- a/packages/core-contracts/CHANGELOG.md +++ b/packages/core-contracts/CHANGELOG.md @@ -1,5 +1,9 @@ # @cloudhal/core-contracts +## 0.6.2 + +No changes in this release. + ## 0.6.1 No changes in this release. diff --git a/packages/core-contracts/package.json b/packages/core-contracts/package.json index 8c86de96..78ad7011 100644 --- a/packages/core-contracts/package.json +++ b/packages/core-contracts/package.json @@ -1,6 +1,6 @@ { "name": "@cloudhal/core-contracts", - "version": "0.6.1", + "version": "0.6.2", "description": "Cloudhal domain contracts: JSON Schema source of truth plus generated TypeScript types", "license": "Apache-2.0", "homepage": "https://cloudhal.dev", diff --git a/packages/core-ts/CHANGELOG.md b/packages/core-ts/CHANGELOG.md index 002c2b59..fc3ea392 100644 --- a/packages/core-ts/CHANGELOG.md +++ b/packages/core-ts/CHANGELOG.md @@ -1,5 +1,41 @@ # @cloudhal/core-ts +## 0.6.2 + +### Patch Changes + +- 7223152: `importSite` (behind `cloudhal pull`, the admin bundle route `cloudhal push` uses, and `cloudhal import`) now checks a bundle's project row before inserting it: it must be the site node's project (`projectId`), a valid Project, with its `id` and `rev` columns matching its body. Before, a bundle could plant any projects row. +- d91ef8f: Dependency patch updates (#115). `@cloudhal/api` depends on Better Auth 1.7.12 and on exactly the versions it uses itself: `@better-auth/core` and `@better-auth/api-key` 1.7.12, `@better-auth/utils` 0.5.0 and `better-call` 1.4.4. `@cloudhal/cloudflare` asks for zod ^4.6.7 (GHSA-mrhx-c7xc-m3w5 is fixed in 4.6.6). `@cloudhal/core-ts` and `@cloudhal/astro-renderer` use marked ^18.1.1. `@cloudhal/core-ts` and `@cloudhal/schedules` use temporal-polyfill 1.0.6. `@cloudhal/astro-renderer` uses vite ^8.3.5. The Studio shipped in `@cloudhal/cli` is built with React 19.3.1, TanStack Router 1.170.46 and TanStack Query 5.104.5. marked 18.1.1 splits a few unusual markdown inputs differently: a blockquote ends before an unquoted line that follows a heading, rule or HTML block, and indented HTML blocks interrupt a paragraph. A stored body like that keeps rendering and shows virtual block ids until its next write. +- f73d05a: RFC-0042 §4, #110: `queryContentEntries` (the API's `GET /entries?where=…`, Studio's lists, MCP `list_entries`) answers `where`, `orderBy`, status, locale, `limit` and `offset` in SQL from the new `entry_list_values` side table once a collection is ready, instead of reading and evaluating the whole collection; results are the shared evaluator's, which stays the fallback (term filters, collections not ready, operands SQL cannot compare exactly) and the oracle of a seeded property suite on SQLite, D1 and Durable Object SQLite. On the 10,000-entry benchmark the store path drops from 124 ms CPU / 10,001 rows (SQLite) and 176 ms / 10,003 rows read (D1) to 0.6 ms / 22 rows and 5.3 ms / 5,068 rows read; a page at offset 4,980 costs about the same as the first. + + The store keeps the table exact. Entry creates, updates, moves and deletes write an entry's rows (its `listFields` values as `resolveFields` reads them) in their own batch, and an original's write rewrites its same-site translations' rows; site writes and field operations that change a collection's list definitions reset its readiness in the same batch, and imports reset the site's. A race never refuses a write: it marks the collection not ready. New `rebuildListValues(sql, options)` is the resumable, budgeted backfill (guarded per chunk, safe to run concurrently; `budget.statements` bounds every statement it issues, `start` rotates where a run begins, `tidy` removes rows of unlisted collections); `updateSite`, finished field operations and `importSite` run it for what they reset, and `openLocalStore` runs it on open. A field operation's revert resets every listed collection whose values its restored bodies change. `deleteContentEntry` behaves as before. + + `revertTagsToTerms` now leaves an entry that was edited after the migration's before-snapshot (by a concurrent write, or before a resumed run) as it is and reports it in `edited`, instead of restoring its earlier fields, status or collection. +- f669266: `importSite`, used by `cloudhal pull`, by the admin bundle route `cloudhal push` uses, and by `cloudhal import`, now runs every check before it writes anything, the bootstrap conflict and the 1000-statement limit included, and plans the media ledger with them. A refused bundle leaves the target as it was; before, node bodies could land ahead of a conflict and snapshots ahead of the size limit. Only a storage failure can stop it between its writes, and importing the bundle again completes it. New checks, each before the first write: + + - Every node body the target lacks must be a valid contract document of the kind of each snapshot ref that points to it, with that ref's id and rev, of the bundle's site (precompiled validators). A body no snapshot references is refused. Before, a body was only checked against its hash, so a crafted bundle could put invalid content behind the published snapshot. + - Node and snapshot ids may not belong to another site of the target, each appears once, and no two nodes share a kind and key or a translation group and locale (the node batch's unique keys). + - Every takedown entry has its fields with their types (`reason`, `legal`, `by`, `at`). + - The media ledger (`snapshot_blobs`) reads the target's own asset bodies, never the bundle's text for a body the target already holds. + + New `planImport(to, bundle, options)` returns what an import would change, without writing: + + - the nodes added, changed and removed; + - the snapshots and node bodies to add; + - whether the project row is new; + - the listed media that are present, missing, of another size or taken down on the target; + - the bundle's takedowns, those whose bytes the target holds (an import deletes them) and those its ledger does not hold yet. + + With `report: true` it returns a bootstrap conflict and missing media instead of throwing them. A node body that is not JSON is refused as `blob is not JSON` instead of with the parser's message. +- 786a455: New `restoreBundle(from, snapshot)`: a site bundle of one snapshot's nodes, rebuilt from the stored node bodies, for `importSite(…, { mode: "replace" })`, which checks it like any bundle. The site's working copy and published pointer become that snapshot's again (`cloudhal import --revert`, RFC-0039). Revs only move forward: a node the site holds at the snapshot's rev or a later one, with other content, comes back at the rev after its current one, so a Studio tab or agent still holding a rev that node had gets a conflict instead of saving over it; a node whose content already is the snapshot's is left as it is. It lists the media those nodes need and carries the store's takedowns among them, so taken-down content stays down; a missing node body, or one that is not the node its snapshot ref names, is refused before anything is written. `exportSite`'s output is unchanged. +- Updated dependencies [d91ef8f] +- Updated dependencies [970c8a1] +- Updated dependencies [6cb7945] +- Updated dependencies [8a30e30] + - @cloudhal/schedules@0.6.2 + - @cloudhal/storage@0.6.2 + - @cloudhal/core-contracts@0.6.2 + ## 0.6.1 ### Patch Changes diff --git a/packages/core-ts/package.json b/packages/core-ts/package.json index e855d2ee..982ef16e 100644 --- a/packages/core-ts/package.json +++ b/packages/core-ts/package.json @@ -1,6 +1,6 @@ { "name": "@cloudhal/core-ts", - "version": "0.6.1", + "version": "0.6.2", "description": "Cloudhal Site Graph core (TypeScript): load/save nodes with optimistic locking, snapshots, diff, publish and rollback; taxonomies, terms, redirects and menus", "license": "Apache-2.0", "homepage": "https://cloudhal.dev", diff --git a/packages/create-cloudhal/CHANGELOG.md b/packages/create-cloudhal/CHANGELOG.md index bf125d36..2fa54dee 100644 --- a/packages/create-cloudhal/CHANGELOG.md +++ b/packages/create-cloudhal/CHANGELOG.md @@ -1,5 +1,16 @@ # create-cloudhal +## 0.6.2 + +### Patch Changes + +- Updated dependencies [d91ef8f] +- Updated dependencies [330b650] +- Updated dependencies [2c18a7c] +- Updated dependencies [33ae911] +- Updated dependencies [68cd5a1] + - @cloudhal/cli@0.6.2 + ## 0.6.1 ### Patch Changes diff --git a/packages/create-cloudhal/package.json b/packages/create-cloudhal/package.json index d7c4adb0..b844b45d 100644 --- a/packages/create-cloudhal/package.json +++ b/packages/create-cloudhal/package.json @@ -1,6 +1,6 @@ { "name": "create-cloudhal", - "version": "0.6.1", + "version": "0.6.2", "description": "Create a Cloudhal site: npm create cloudhal@latest", "license": "Apache-2.0", "homepage": "https://cloudhal.dev", diff --git a/packages/mcp-server/CHANGELOG.md b/packages/mcp-server/CHANGELOG.md index a90aac5e..e304e6f2 100644 --- a/packages/mcp-server/CHANGELOG.md +++ b/packages/mcp-server/CHANGELOG.md @@ -1,5 +1,28 @@ # @cloudhal/mcp-server +## 0.6.2 + +### Patch Changes + +- f73d05a: `list_entries` with `orderBy` and `limit` lets the store page (in SQL once the collection's list values are ready, RFC-0042 §4, #110) instead of loading every match. Arguments, cursors and output are unchanged; without `orderBy` the list keeps its last-updated order. +- 77fa9e5: render_page's long-line and input-label checks handle whitespace correctly again. A plain template literal ate the backslash, so the in-page script received `/s/` and `/s+/` instead of `/\s/` and `/\s+/`. As a result, long-line counted the letter "s" as blank and every real space and indentation run as text. input-label split `aria-labelledby` on the letter "s" and reported labelled inputs as unlabelled. The check parts are now `String.raw` templates. +- Updated dependencies [7223152] +- Updated dependencies [d91ef8f] +- Updated dependencies [970c8a1] +- Updated dependencies [f73d05a] +- Updated dependencies [6cb7945] +- Updated dependencies [f669266] +- Updated dependencies [786a455] +- Updated dependencies [8a30e30] + - @cloudhal/core-ts@0.6.2 + - @cloudhal/schedules@0.6.2 + - @cloudhal/astro-renderer@0.6.2 + - @cloudhal/storage@0.6.2 + - @cloudhal/analytics@0.6.2 + - @cloudhal/comments@0.6.2 + - @cloudhal/agent-runtime@0.6.2 + - @cloudhal/core-contracts@0.6.2 + ## 0.6.1 ### Patch Changes diff --git a/packages/mcp-server/package.json b/packages/mcp-server/package.json index 20586536..eb9e600e 100644 --- a/packages/mcp-server/package.json +++ b/packages/mcp-server/package.json @@ -1,6 +1,6 @@ { "name": "@cloudhal/mcp-server", - "version": "0.6.1", + "version": "0.6.2", "description": "Cloudhal MCP server: semantic site tools (pages, articles, snapshots, preview, publish) governed by the policy engine", "license": "Apache-2.0", "homepage": "https://cloudhal.dev", diff --git a/packages/schedules/CHANGELOG.md b/packages/schedules/CHANGELOG.md index 9147e114..680354dd 100644 --- a/packages/schedules/CHANGELOG.md +++ b/packages/schedules/CHANGELOG.md @@ -1,5 +1,17 @@ # @cloudhal/schedules +## 0.6.2 + +### Patch Changes + +- d91ef8f: Dependency patch updates (#115). `@cloudhal/api` depends on Better Auth 1.7.12 and on exactly the versions it uses itself: `@better-auth/core` and `@better-auth/api-key` 1.7.12, `@better-auth/utils` 0.5.0 and `better-call` 1.4.4. `@cloudhal/cloudflare` asks for zod ^4.6.7 (GHSA-mrhx-c7xc-m3w5 is fixed in 4.6.6). `@cloudhal/core-ts` and `@cloudhal/astro-renderer` use marked ^18.1.1. `@cloudhal/core-ts` and `@cloudhal/schedules` use temporal-polyfill 1.0.6. `@cloudhal/astro-renderer` uses vite ^8.3.5. The Studio shipped in `@cloudhal/cli` is built with React 19.3.1, TanStack Router 1.170.46 and TanStack Query 5.104.5. marked 18.1.1 splits a few unusual markdown inputs differently: a blockquote ends before an unquoted line that follows a heading, rule or HTML block, and indented HTML blocks interrupt a paragraph. A stored body like that keeps rendering and shows virtual block ids until its next write. +- 8a30e30: The `./testing` subpath now ships. The published packages pointed `./testing` at `dist/src/testing.js` and `.d.ts`, but the build left those files out, so importing `@cloudhal/{storage,analytics,comments,schedules}/testing` failed with ERR_MODULE_NOT_FOUND. The suites run on your own vitest, 3 or later, which is an optional peer dependency. `@cloudhal/storage`'s Miniflare helpers also load your own `miniflare`, an optional peer of any version. The ranges are wide on purpose. When a direct dependency's optional peer does not match the copy in your project, npm stops with ERESOLVE, even if nothing imports `./testing`. No semver range matches the prerelease miniflare that wrangler currently brings in, so with a narrower range npm would install a second miniflare beside it. +- Updated dependencies [970c8a1] +- Updated dependencies [6cb7945] +- Updated dependencies [8a30e30] + - @cloudhal/storage@0.6.2 + - @cloudhal/core-contracts@0.6.2 + ## 0.6.1 ### Patch Changes diff --git a/packages/schedules/package.json b/packages/schedules/package.json index f4944054..038f2f8a 100644 --- a/packages/schedules/package.json +++ b/packages/schedules/package.json @@ -1,6 +1,6 @@ { "name": "@cloudhal/schedules", - "version": "0.6.1", + "version": "0.6.2", "description": "Cloudhal schedules (RFC-0008): the time model, the RRULE subset and its sentences, releases (pin, closure, rl1: hash, compose, conflicts, state machine), automation and run state, taint and budget accounting, the Scheduler and runDue, and the SQLite/D1 store. Worker-safe.", "license": "Apache-2.0", "homepage": "https://cloudhal.dev", diff --git a/packages/storage/CHANGELOG.md b/packages/storage/CHANGELOG.md index 5210fe96..7491e144 100644 --- a/packages/storage/CHANGELOG.md +++ b/packages/storage/CHANGELOG.md @@ -1,5 +1,14 @@ # @cloudhal/storage +## 0.6.2 + +### Patch Changes + +- 970c8a1: createMiniflareDoSqlite() sends its Durable Object calls over kept-alive connections instead of opening a new TCP connection per call through Miniflare 4's dispatchFetch, so long suites no longer exhaust local ports on macOS (#116). +- 6cb7945: Migration `0029_entry_list_values` (RFC-0042 §4, #110): `entry_list_values`, the indexed list-field values of entries (field, presence, number, text, collection-sort key, creation time, node, locale and status) with a query index and a per-node index, and `entry_list_state`, each listed collection's readiness (definition fingerprint, ready flag, backfill epoch and cursor). DDL only; existing data is untouched. +- 8a30e30: The `./testing` subpath now ships. The published packages pointed `./testing` at `dist/src/testing.js` and `.d.ts`, but the build left those files out, so importing `@cloudhal/{storage,analytics,comments,schedules}/testing` failed with ERR_MODULE_NOT_FOUND. The suites run on your own vitest, 3 or later, which is an optional peer dependency. `@cloudhal/storage`'s Miniflare helpers also load your own `miniflare`, an optional peer of any version. The ranges are wide on purpose. When a direct dependency's optional peer does not match the copy in your project, npm stops with ERESOLVE, even if nothing imports `./testing`. No semver range matches the prerelease miniflare that wrangler currently brings in, so with a narrower range npm would install a second miniflare beside it. +- @cloudhal/core-contracts@0.6.2 + ## 0.6.1 ### Patch Changes diff --git a/packages/storage/package.json b/packages/storage/package.json index 47954b75..cc1ee338 100644 --- a/packages/storage/package.json +++ b/packages/storage/package.json @@ -1,6 +1,6 @@ { "name": "@cloudhal/storage", - "version": "0.6.1", + "version": "0.6.2", "description": "Cloudhal storage interfaces (SQL driver, blob store) with Cloudflare D1/R2/Durable Object SQLite and local SQLite/filesystem adapters", "license": "Apache-2.0", "homepage": "https://cloudhal.dev",