@clubedge/create-clubedge-app 0.2.0 → 0.2.1

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
@@ -2,6 +2,11 @@
2
2
 
3
3
  All notable changes to `create-clubedge-app` are documented here.
4
4
 
5
+ ## 0.2.1
6
+
7
+ - Publish the default Starter pin in the `clubedge` field of `package.json`. The CLI and release workflow read it from there, and the npm registry exposes it so the website always shows the Starter each CLI version scaffolds.
8
+ - Optionally trigger a website rebuild after a release when the `SITE_DEPLOY_HOOK` secret is configured.
9
+
5
10
  ## 0.2.0
6
11
 
7
12
  - Default to Starter `v0.2.0`, which adds project identity in `site.json`, dashboard protection, rate-limited sign-in and sign-up, and lazy environment validation.
package/README.md CHANGED
@@ -12,7 +12,7 @@ The CLI downloads a tested Starter release, names the generated project, creates
12
12
  Each CLI release is tested against one specific Starter release:
13
13
 
14
14
  ```text
15
- create-clubedge-app v0.2.0
15
+ create-clubedge-app v0.2.1
16
16
  |
17
17
  v
18
18
  Clubedge Starter v0.2.0
@@ -23,7 +23,7 @@ The current relationship is:
23
23
 
24
24
  | CLI release | Default Starter release | Meaning |
25
25
  | --- | --- | --- |
26
- | `create-clubedge-app@0.2.0` | `clubedge-starter@v0.2.0` | The CLI's required, tested default |
26
+ | `create-clubedge-app@0.2.1` | `clubedge-starter@v0.2.0` | The CLI's required, tested default |
27
27
 
28
28
  This means the same CLI version always scaffolds the same Starter revision by default. The CLI does not silently follow Starter `main`.
29
29
 
package/bin/create.mjs CHANGED
@@ -8,14 +8,17 @@ import { basename, dirname, join, resolve } from "node:path";
8
8
  import process from "node:process";
9
9
  import { pathToFileURL } from "node:url";
10
10
 
11
- const starterRepository = "Clubedge/clubedge-starter";
12
- const defaultStarterRef = "v0.2.0";
13
- const defaultStarterCommit = "db15901da90d8d8a190d158c895dfe76c172b415";
11
+ // package.json is the single source for the version and the tested Starter pin. It is
12
+ // published with the package, so the npm registry exposes exactly what each release scaffolds.
13
+ const packageManifest = JSON.parse(await readFile(new URL("../package.json", import.meta.url), "utf8"));
14
+ const packageVersion = packageManifest.version;
15
+ const {
16
+ starterRepository,
17
+ starterRef: defaultStarterRef,
18
+ starterCommit: defaultStarterCommit,
19
+ } = packageManifest.clubedge;
14
20
  const siteUrl = "https://clubedge.live";
15
21
  const cliUrl = "https://starter.clubedge.live";
16
- const packageVersion = JSON.parse(
17
- await readFile(new URL("../package.json", import.meta.url), "utf8"),
18
- ).version;
19
22
 
20
23
  /* ------------------------------------------------------------------ */
21
24
  /* Branding: big block-letter banner */
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@clubedge/create-clubedge-app",
3
- "version": "0.2.0",
3
+ "version": "0.2.1",
4
4
  "description": "Create a Next.js application from the Clubedge Starter reference implementation.",
5
5
  "type": "module",
6
6
  "packageManager": "pnpm@10.9.0",
@@ -17,6 +17,11 @@
17
17
  "engines": {
18
18
  "node": ">=22.12.0"
19
19
  },
20
+ "clubedge": {
21
+ "starterRepository": "Clubedge/clubedge-starter",
22
+ "starterRef": "v0.2.0",
23
+ "starterCommit": "db15901da90d8d8a190d158c895dfe76c172b415"
24
+ },
20
25
  "license": "Apache-2.0",
21
26
  "repository": {
22
27
  "type": "git",