@clubedge/create-clubedge-app 0.1.10 → 0.1.11

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.1.11
6
+
7
+ - Generate the published-package smoke-test project by extracting and invoking the exact npm tarball.
8
+ - Fail the generation step if the generated project manifest is missing.
9
+
5
10
  ## 0.1.10
6
11
 
7
12
  - Make the published-package smoke test resilient to npm registry propagation delays by retrying the exact package tarball.
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.1.10
15
+ create-clubedge-app v0.1.11
16
16
  |
17
17
  v
18
18
  Clubedge Starter v0.1.1
@@ -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.1.10` | `clubedge-starter@v0.1.1` | The CLI's required, tested default |
26
+ | `create-clubedge-app@0.1.11` | `clubedge-starter@v0.1.1` | 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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@clubedge/create-clubedge-app",
3
- "version": "0.1.10",
3
+ "version": "0.1.11",
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",