create-payload-canvas 0.6.1 → 0.7.0-next.0

package/README.md

@@ -6,7 +6,9 @@
 
 Creates a new Payload CMS website builder project from the Payload Canvas starter.
 
-Requirements: Node.js 20.9 or later, a running PostgreSQL server, and pnpm (npm works too). The starter itself is downloaded from GitHub, so the first run needs network access.
+This is the Payload 4 line (`create-payload-canvas@next`): projects get Payload 4 beta and `payload-canvas@next`. For Payload 3, use `create-payload-canvas@latest`.
+
+Requirements: Node.js 24.22.1 or later, a running PostgreSQL server, and pnpm (npm works too). The starter itself is downloaded from GitHub, so the first run needs network access.
 
 ```bash
 pnpm create payload-canvas my-website
@@ -69,7 +71,7 @@ For each feature that is off, the CLI deletes its files and its npm packages fro
 | `--no-look`, `--no-nav`, `--no-dashboard`, `--no-demo`, `--no-ai`, `--no-gallery`, `--no-workflows` | Leave out a starter feature. See [Features](#features). `--no-demo` also turns off seeding. |
 | `--reviews` | Add Google reviews, which is off by default. Every feature also takes `--<feature>` and `--no-<feature>`. |
 | `--github` | Download the starter from GitHub, even when the CLI runs inside a checkout. |
-| `--ref <name>` | Branch or tag to download. Default `main`. |
+| `--ref <name>` | Branch or tag to download. Default: the release tag of this CLI version (`v0.7.0-next.0` on the Payload 4 next line, `main` on the Payload 3 line). |
 | `--packages <path>` | Path to a checkout of the repo. The CLI packs the `payload-canvas` package from there. |
 | `-h`, `--help` | Show help. |
 
@@ -78,7 +80,7 @@ For each feature that is off, the CLI deletes its files and its npm packages fro
 | Case | `payload-canvas` in the new project |
 |---|---|
 | The CLI runs inside a checkout, or you pass `--packages <path>` | a `file:./.tarballs/...` tarball, packed with `pnpm pack` (it builds `dist/` first). Commit `.tarballs/` with the project. |
-| Neither | The version on npm (`^0.6.1`). |
+| Neither | The version on npm (`^0.6.0`). |
 
 Without `--packages`, and outside a checkout, the CLI checks the npm registry first. If the package is not on npm (for example, a `--ref` with an unreleased version), it stops before it writes any file and tells you to use `--packages <path>` or `--no-install`.
 

package/dist/config.js

@@ -1,15 +1,18 @@
 // The GitHub repo that hosts Payload Canvas. Change it here if the repo moves.
 export const GITHUB_OWNER = 'jon8800';
 export const GITHUB_REPO = 'payload-canvas';
-export const DEFAULT_REF = 'main';
+// The Payload 4 next line downloads the starter from its release tag, so a project matches the
+// published `payload-canvas@next`. Keep it equal to `v${version}` of this package
+// (scripts/check-next-release.mjs checks it). The Payload 3 line on `main` uses 'main'.
+export const DEFAULT_REF = 'v0.7.0-next.0';
 export const STARTER_SUBDIR = 'apps/starter';
 // Guides that the starter's .env.example points to. They live at the repo root.
 export const DOCS_SUBDIR = 'docs/ai';
 export function tarballUrl(ref) {
     return `https://codeload.github.com/${GITHUB_OWNER}/${GITHUB_REPO}/tar.gz/${ref}`;
 }
-// Version range for the payload-canvas package when it comes from npm.
-export const PUBLISHED_VERSION = '^0.6.1';
+// Version range for the payload-canvas package when it comes from npm: the Payload 4 next line.
+export const PUBLISHED_VERSION = '^0.7.0-next.0';
 // The package the starter depends on: its npm name and its folder under `packages/` in the repo.
 export const BUILDER_PACKAGE = { name: 'payload-canvas', dir: 'payload-canvas' };
 // Files and folders of the starter that only make sense inside the repo. The CLI does not copy them.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-payload-canvas",
-  "version": "0.6.1",
+  "version": "0.7.0-next.0",
   "description": "Create a new Payload CMS website with Payload Canvas: the visual page builder, Postgres, a seeded demo and the AI guides.",
   "keywords": [
     "payload",
@@ -33,7 +33,8 @@
     "LICENSE"
   ],
   "publishConfig": {
-    "access": "public"
+    "access": "public",
+    "tag": "next"
   },
   "dependencies": {
     "@clack/prompts": "^1.8.1",
@@ -49,7 +50,7 @@
     "typescript": "^7.0.2"
   },
   "engines": {
-    "node": ">=20.9.0"
+    "node": ">=24.22.1"
   },
   "scripts": {
     "build": "node -e \"require('node:fs').rmSync('dist',{recursive:true,force:true})\" && tsc",