From a2059d0afeb9ade3049e47d9a74f9f6d29aebaf1 Mon Sep 17 00:00:00 2001 From: Jeremy Bise Date: Sun, 15 Nov 2026 18:43:41 -0500 Subject: [PATCH] chore: version 0.1.0-next.3 `npm run changeset -- version`, with the lockfile's workspace versions following, as for 0.1.0-next.2. It carries Phase 6a's forms (#14) and the packages' own changelogs (#13). Co-Authored-By: Claude Opus 5.5 --- .changeset/{ => pre}/forms-6a.md | 0 .changeset/{ => pre}/ship-changelogs.md | 0 PLAN.md | 10 +++++----- apps/playground/package.json | 2 +- apps/site/package.json | 2 +- package-lock.json | 16 ++++++++-------- packages/admin/CHANGELOG.md | 10 ++++++++++ packages/admin/package.json | 4 ++-- packages/astro/CHANGELOG.md | 11 +++++++++++ packages/astro/package.json | 6 +++--- packages/core/CHANGELOG.md | 7 +++++++ packages/core/package.json | 2 +- 12 files changed, 49 insertions(+), 21 deletions(-) rename .changeset/{ => pre}/forms-6a.md (100%) rename .changeset/{ => pre}/ship-changelogs.md (100%) diff --git a/.changeset/forms-6a.md b/.changeset/pre/forms-6a.md similarity index 100% rename from .changeset/forms-6a.md rename to .changeset/pre/forms-6a.md diff --git a/.changeset/ship-changelogs.md b/.changeset/pre/ship-changelogs.md similarity index 100% rename from .changeset/ship-changelogs.md rename to .changeset/pre/ship-changelogs.md diff --git a/PLAN.md b/PLAN.md index edb35b0..a7e831e 100644 --- a/PLAN.md +++ b/PLAN.md @@ -39,9 +39,9 @@ The short list, in order. Tick or remove an item as it lands; the history stays - [x] Jeremy confirmed the other nine calls as recommended (2026-11-15). - [x] Build this repository's half on `claude/forms-6a` (2026-11-15), then the cloud's (2026-11-15, in `vesper-cloud`). See "Phase 6a: progress". - [x] Jeremy's OK (2026-11-15) for the cloud's new bindings, pushing both branches, and the staging deploy: done that day. Staging is migrated and deployed; `SECRETS_KEY` isn't set there yet. -- [ ] Open the PRs, so CI runs (it runs only on pull requests in both repositories). -- [ ] The end-to-end check on staging: `SECRETS_KEY` on both staging Workers (Jeremy's), and a site with forms that the staging cloud can read. -- [ ] Release `0.1.0-next.3`. wcpl.net launches on it. +- [x] The PRs: #14 here, merged 2026-11-15 after #13, and VesperCMS/vespercms-cloud#3. +- [x] Staging's check dropped (Jeremy, 2026-11-15: "just go live", as no site runs on the cloud yet). He saw the form, the API, routing, a confirmation and the inbox work by hand against the real API and app locally first. The cloud went to production that day, at `3ad9a2d`. +- [ ] Release `0.1.0-next.3`: versioned here; the Release workflow publishes it from `main`. wcpl.net launches on it. **Next phase** - [ ] Phase 5, Billing and ops. Before it starts, Jeremy decides spec §13.4: the final prices, from the cloud's measured cost (the addendum's numbers are placeholders). Bring him options; never pick. @@ -80,7 +80,7 @@ Blocks (proposed, decided and built 2026-10-26): "Blocks: lists of different kin ## Phase 6a: progress -Started 2026-11-15, the day its calls were confirmed. The steps are the design's order of work, below. Built on `claude/forms-6a` (branched from #13's head, which should merge first), not yet pushed. +Started 2026-11-15, the day its calls were confirmed. The steps are the design's order of work, below. Built on `claude/forms-6a` (branched from #13's head) and merged in #14 on 2026-11-15, after #13. | Step | What | Status | |---|---|---| @@ -89,7 +89,7 @@ Started 2026-11-15, the day its calls were confirmed. The steps are the design's | 3 | `vespercms/forms`, `virtual:vesper/forms`, `
` and its script, the dev capture | Built. The script is 5 KB gzipped (the test holds it to 8). A build with forms and no cloud project warns | | 4 | The contract's `forms` section, the fake's endpoints, the playground's form, e2e, docs | Built: eight contract cases, passing against the fake and the real cloud; `e2e/cloud/forms.spec.ts` (eight tests, JavaScript on and off); `site/forms.mdoc`, the README and the reference; `vesper agents` says how a site's forms work | | 5–8 | The cloud's half | In `vesper-cloud`: see its PLAN.md | -| 9 | The changeset and `0.1.0-next.3` | Waits for the cloud's staging check | +| 9 | The changeset and `0.1.0-next.3` | Versioned 2026-11-15, after the cloud went to production (`3ad9a2d`); the Release workflow publishes it | **Found while building:** - **A redraw on blur moved Send under a click.** Clearing an error or the summary as a field was left shifted the page between the button's mousedown and mouseup, so the click missed and nothing was sent. The script now adds errors and changes the summary only on submit; an error goes as its answer is fixed (DECISIONS.md, "'s script redraws nothing as a field is left"). diff --git a/apps/playground/package.json b/apps/playground/package.json index c816aef..df07a63 100644 --- a/apps/playground/package.json +++ b/apps/playground/package.json @@ -14,7 +14,7 @@ "dependencies": { "@astrojs/markdoc": "^2.1.0", "@astrojs/mdx": "^8.1.0", - "vespercms": "0.1.0-next.2", + "vespercms": "0.1.0-next.3", "astro": "^7.4.0", "lucide": "^1.59.0" }, diff --git a/apps/site/package.json b/apps/site/package.json index 5f5f836..628208f 100644 --- a/apps/site/package.json +++ b/apps/site/package.json @@ -16,7 +16,7 @@ "dependencies": { "@astrojs/markdoc": "^2.1.0", "@fontsource/figtree": "^5.3.0", - "vespercms": "0.1.0-next.2", + "vespercms": "0.1.0-next.3", "astro": "^7.4.0", "lucide": "^1.59.0", "micromark": "^4.0.3" diff --git a/package-lock.json b/package-lock.json index dcc17f6..1639c4b 100644 --- a/package-lock.json +++ b/package-lock.json @@ -48,7 +48,7 @@ "@astrojs/mdx": "^8.1.0", "astro": "^7.4.0", "lucide": "^1.59.0", - "vespercms": "0.1.0-next.2" + "vespercms": "0.1.0-next.3" }, "devDependencies": { "@astrojs/check": "^0.9.10" @@ -63,7 +63,7 @@ "astro": "^7.4.0", "lucide": "^1.59.0", "micromark": "^4.0.3", - "vespercms": "0.1.0-next.2" + "vespercms": "0.1.0-next.3" }, "devDependencies": { "@astrojs/check": "^0.9.10" @@ -13255,7 +13255,7 @@ }, "packages/admin": { "name": "@vespercms/admin", - "version": "0.1.0-next.2", + "version": "0.1.0-next.3", "license": "MIT", "dependencies": { "@tiptap/core": "^3.32.0", @@ -13265,7 +13265,7 @@ "@tiptap/pm": "^3.32.0", "@tiptap/react": "^3.32.0", "@tiptap/starter-kit": "^3.32.0", - "@vespercms/core": "0.1.0-next.2", + "@vespercms/core": "0.1.0-next.3", "dompurify": "^3.4.17", "maplibre-gl": "^6.14.0", "react-aria-components": "^1.22.1" @@ -13283,12 +13283,12 @@ }, "packages/astro": { "name": "vespercms", - "version": "0.1.0-next.2", + "version": "0.1.0-next.3", "license": "MIT", "dependencies": { "@markdoc/markdoc": "^0.5.10", - "@vespercms/admin": "0.1.0-next.2", - "@vespercms/core": "0.1.0-next.2", + "@vespercms/admin": "0.1.0-next.3", + "@vespercms/core": "0.1.0-next.3", "axe-core": "^4.14.0", "jsdom": "^30.1.3", "pagefind": "^1.5.2" @@ -13317,7 +13317,7 @@ }, "packages/core": { "name": "@vespercms/core", - "version": "0.1.0-next.2", + "version": "0.1.0-next.3", "license": "MIT", "dependencies": { "@markdoc/markdoc": "^0.5.10", diff --git a/packages/admin/CHANGELOG.md b/packages/admin/CHANGELOG.md index d8a386a..9cc2b7e 100644 --- a/packages/admin/CHANGELOG.md +++ b/packages/admin/CHANGELOG.md @@ -1,5 +1,15 @@ # @vespercms/admin +## 0.1.0-next.3 + +### Patch Changes + +- 2a1602b: Forms (Phase 6a): define a form in `src/forms.config.ts` with `defineForm` from `vespercms/forms`, and put it on a page with `` from `vespercms/components`. It works without JavaScript, posting to Vesper Cloud, which sends the browser back to the page's thanks message or shows the form again with the answers kept; with JavaScript, Vesper's own 5 KB script checks answers, posts without leaving the page and moves focus to the error summary or the thanks message. Fields can be text (`tel` is new), numbers, dates and times, choices, lists of choices (`checkboxes`), yes or no (`checkbox`) and groups. The build refuses what a form can't take and warns that a `.refine()` never runs on a submission; without a cloud project each form says it isn't connected yet. In `astro dev` posts are kept in `.vesper/forms/` and nothing is sent. `@vespercms/core/forms` has the reading, routing, confirmation and drawing the cloud shares, and `runCloudContract` a forms section. File uploads come in Phase 6b. +- 448d685: Each package includes its `CHANGELOG.md`, so `node_modules/vespercms/CHANGELOG.md` says what changed before you update. +- Updated dependencies [2a1602b] +- Updated dependencies [448d685] + - @vespercms/core@0.1.0-next.3 + ## 0.1.0-next.2 ### Patch Changes diff --git a/packages/admin/package.json b/packages/admin/package.json index da24488..79e3511 100644 --- a/packages/admin/package.json +++ b/packages/admin/package.json @@ -1,6 +1,6 @@ { "name": "@vespercms/admin", - "version": "0.1.0-next.2", + "version": "0.1.0-next.3", "description": "The Vesper studio: the editor UI served at /admin, one bundle for every storage mode.", "license": "MIT", "homepage": "https://vespercms.com", @@ -47,7 +47,7 @@ "@tiptap/pm": "^3.32.0", "@tiptap/react": "^3.32.0", "@tiptap/starter-kit": "^3.32.0", - "@vespercms/core": "0.1.0-next.2", + "@vespercms/core": "0.1.0-next.3", "dompurify": "^3.4.17", "maplibre-gl": "^6.14.0", "react-aria-components": "^1.22.1" diff --git a/packages/astro/CHANGELOG.md b/packages/astro/CHANGELOG.md index 3efb8ed..25b18fc 100644 --- a/packages/astro/CHANGELOG.md +++ b/packages/astro/CHANGELOG.md @@ -1,5 +1,16 @@ # vespercms +## 0.1.0-next.3 + +### Patch Changes + +- 2a1602b: Forms (Phase 6a): define a form in `src/forms.config.ts` with `defineForm` from `vespercms/forms`, and put it on a page with `` from `vespercms/components`. It works without JavaScript, posting to Vesper Cloud, which sends the browser back to the page's thanks message or shows the form again with the answers kept; with JavaScript, Vesper's own 5 KB script checks answers, posts without leaving the page and moves focus to the error summary or the thanks message. Fields can be text (`tel` is new), numbers, dates and times, choices, lists of choices (`checkboxes`), yes or no (`checkbox`) and groups. The build refuses what a form can't take and warns that a `.refine()` never runs on a submission; without a cloud project each form says it isn't connected yet. In `astro dev` posts are kept in `.vesper/forms/` and nothing is sent. `@vespercms/core/forms` has the reading, routing, confirmation and drawing the cloud shares, and `runCloudContract` a forms section. File uploads come in Phase 6b. +- 448d685: Each package includes its `CHANGELOG.md`, so `node_modules/vespercms/CHANGELOG.md` says what changed before you update. +- Updated dependencies [2a1602b] +- Updated dependencies [448d685] + - @vespercms/core@0.1.0-next.3 + - @vespercms/admin@0.1.0-next.3 + ## 0.1.0-next.2 ### Patch Changes diff --git a/packages/astro/package.json b/packages/astro/package.json index e207ed6..9279351 100644 --- a/packages/astro/package.json +++ b/packages/astro/package.json @@ -1,6 +1,6 @@ { "name": "vespercms", - "version": "0.1.0-next.2", + "version": "0.1.0-next.3", "description": "The Vesper integration for Astro: the studio at /admin, schema helpers and config.", "license": "MIT", "homepage": "https://vespercms.com", @@ -84,8 +84,8 @@ "//dependencies": "axe-core runs the build's accessibility checks (spec §6.18, layer 2), the same engine as the e2e suite; jsdom is the DOM it runs in without a browser, matched against Chromium (DECISIONS.md). pagefind indexes the site for search (spec §6.19, D23): a regular dependency because search is on by default, with a 58 MB binary for the build machine's platform, as Starlight ships it. All three load only in astro:build:done.", "dependencies": { "@markdoc/markdoc": "^0.5.10", - "@vespercms/admin": "0.1.0-next.2", - "@vespercms/core": "0.1.0-next.2", + "@vespercms/admin": "0.1.0-next.3", + "@vespercms/core": "0.1.0-next.3", "axe-core": "^4.14.0", "jsdom": "^30.1.3", "pagefind": "^1.5.2" diff --git a/packages/core/CHANGELOG.md b/packages/core/CHANGELOG.md index 0d77a47..1259f13 100644 --- a/packages/core/CHANGELOG.md +++ b/packages/core/CHANGELOG.md @@ -1,5 +1,12 @@ # @vespercms/core +## 0.1.0-next.3 + +### Patch Changes + +- 2a1602b: Forms (Phase 6a): define a form in `src/forms.config.ts` with `defineForm` from `vespercms/forms`, and put it on a page with `` from `vespercms/components`. It works without JavaScript, posting to Vesper Cloud, which sends the browser back to the page's thanks message or shows the form again with the answers kept; with JavaScript, Vesper's own 5 KB script checks answers, posts without leaving the page and moves focus to the error summary or the thanks message. Fields can be text (`tel` is new), numbers, dates and times, choices, lists of choices (`checkboxes`), yes or no (`checkbox`) and groups. The build refuses what a form can't take and warns that a `.refine()` never runs on a submission; without a cloud project each form says it isn't connected yet. In `astro dev` posts are kept in `.vesper/forms/` and nothing is sent. `@vespercms/core/forms` has the reading, routing, confirmation and drawing the cloud shares, and `runCloudContract` a forms section. File uploads come in Phase 6b. +- 448d685: Each package includes its `CHANGELOG.md`, so `node_modules/vespercms/CHANGELOG.md` says what changed before you update. + ## 0.1.0-next.2 ### Patch Changes diff --git a/packages/core/package.json b/packages/core/package.json index 389bc74..b69a9f1 100644 --- a/packages/core/package.json +++ b/packages/core/package.json @@ -1,6 +1,6 @@ { "name": "@vespercms/core", - "version": "0.1.0-next.2", + "version": "0.1.0-next.3", "description": "Vesper's framework-free core: schema introspection, manifest, serializers and the storage adapter interface.", "license": "MIT", "homepage": "https://vespercms.com",