@clubedge/create-clubedge-app 0.1.5 → 0.1.10

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.
Files changed (4) hide show
  1. package/CHANGELOG.md +22 -0
  2. package/README.md +12 -12
  3. package/bin/create.mjs +3 -3
  4. package/package.json +4 -4
package/CHANGELOG.md CHANGED
@@ -2,6 +2,28 @@
2
2
 
3
3
  All notable changes to `create-clubedge-app` are documented here.
4
4
 
5
+ ## 0.1.10
6
+
7
+ - Make the published-package smoke test resilient to npm registry propagation delays by retrying the exact package tarball.
8
+
9
+ ## 0.1.9
10
+
11
+ - Use npm Trusted Publishing with GitHub Actions OIDC for releases.
12
+ - Use an npm CLI version supported by Trusted Publishing and remove the token-based publish dependency.
13
+
14
+ ## 0.1.8
15
+
16
+ - Correct the pinned Starter commit to the commit actually resolved by the immutable `v0.1.1` tag.
17
+
18
+ ## 0.1.7
19
+
20
+ - Pin the default Starter reference to the tested `v0.1.1` release, including the corrected browser contract.
21
+
22
+ ## 0.1.6
23
+
24
+ - Move the CLI and Starter repository references to the `Clubedge` GitHub organization.
25
+ - Update package metadata, documentation, tests, and generated provenance for the organization repositories.
26
+
5
27
  ## 0.1.5
6
28
 
7
29
  - Verify the default Starter tag resolves to its expected commit and record that commit in generated metadata.
package/README.md CHANGED
@@ -1,9 +1,9 @@
1
1
  # create-clubedge-app
2
2
 
3
- [![CI](https://github.com/yassine-ahmed/create-clubedge-app/actions/workflows/ci.yml/badge.svg?branch=main)](https://github.com/yassine-ahmed/create-clubedge-app/actions/workflows/ci.yml)
3
+ [![CI](https://github.com/Clubedge/create-clubedge-app/actions/workflows/ci.yml/badge.svg?branch=main)](https://github.com/Clubedge/create-clubedge-app/actions/workflows/ci.yml)
4
4
  [![License: Apache-2.0](https://img.shields.io/badge/License-Apache--2.0-blue.svg)](LICENSE)
5
5
 
6
- Create a Next.js application from the [Clubedge Starter](https://github.com/yassine-ahmed/clubedge-starter) reference implementation.
6
+ Create a Next.js application from the [Clubedge Starter](https://github.com/Clubedge/clubedge-starter) reference implementation.
7
7
 
8
8
  The CLI downloads a tested Starter release, names the generated project, creates `apps/web/.env.local` from the example, initializes Git, and installs dependencies. The Starter remains the source of truth for the generated architecture.
9
9
 
@@ -12,23 +12,23 @@ 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.5
15
+ create-clubedge-app v0.1.10
16
16
  |
17
17
  v
18
- Clubedge Starter v0.1.0
19
- commit 4334121e4ce46a331d7c542c6025fdfe2b8c0657
18
+ Clubedge Starter v0.1.1
19
+ commit 0be0c18d41f01cd011c576fb65c25711081b8ad4
20
20
  ```
21
21
 
22
22
  The current relationship is:
23
23
 
24
24
  | CLI release | Default Starter release | Meaning |
25
25
  | --- | --- | --- |
26
- | `create-clubedge-app@0.1.5` | `clubedge-starter@v0.1.0` | The CLI's required, tested default |
26
+ | `create-clubedge-app@0.1.10` | `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
 
30
- The `v0.1.0` tag is expected to resolve to commit
31
- `4334121e4ce46a331d7c542c6025fdfe2b8c0657`. The CLI verifies this before
30
+ The `v0.1.1` tag is expected to resolve to commit
31
+ `0be0c18d41f01cd011c576fb65c25711081b8ad4`. The CLI verifies this before
32
32
  scaffolding with the default reference and fails rather than silently using a
33
33
  moved tag.
34
34
 
@@ -73,7 +73,7 @@ pnpm dlx @clubedge/create-clubedge-app
73
73
  ```text
74
74
  Usage: pnpm dlx @clubedge/create-clubedge-app [project-directory] [options]
75
75
 
76
- --ref <ref> Select a starter tag, branch, or commit (default: v0.1.0)
76
+ --ref <ref> Select a starter tag, branch, or commit (default: v0.1.1)
77
77
  --no-install Skip pnpm install
78
78
  --no-git Skip Git initialization
79
79
  -h, --help Show help
@@ -87,9 +87,9 @@ pnpm dlx @clubedge/create-clubedge-app my-app --ref <starter-tag-or-commit>
87
87
  pnpm dlx @clubedge/create-clubedge-app my-app --no-install
88
88
  ```
89
89
 
90
- The target directory must be empty or not exist. The CLI will not delete or overwrite files in a non-empty target directory. The default is the tested `v0.1.0` Starter release, so the same CLI version produces the same Starter revision. Use `--ref` to explicitly select a tag, branch, or commit.
90
+ The target directory must be empty or not exist. The CLI will not delete or overwrite files in a non-empty target directory. The default is the tested `v0.1.1` Starter release, so the same CLI version produces the same Starter revision. Use `--ref` to explicitly select a tag, branch, or commit.
91
91
 
92
- The default is the tested Starter release tag `v0.1.0`. Every generated project records its CLI version, Starter repository, exact Starter ref, and resolved Starter commit in `package.json` and `README.md`.
92
+ The default is the tested Starter release tag `v0.1.1`. Every generated project records its CLI version, Starter repository, exact Starter ref, and resolved Starter commit in `package.json` and `README.md`.
93
93
 
94
94
  Use `--ref` only when you intentionally want a different Starter revision:
95
95
 
@@ -101,7 +101,7 @@ pnpm dlx @clubedge/create-clubedge-app my-app
101
101
  pnpm dlx @clubedge/create-clubedge-app my-app --ref main
102
102
 
103
103
  # Reproduce a specific Starter release or commit
104
- pnpm dlx @clubedge/create-clubedge-app my-app --ref v0.1.0
104
+ pnpm dlx @clubedge/create-clubedge-app my-app --ref v0.1.1
105
105
  pnpm dlx @clubedge/create-clubedge-app my-app --ref <commit-sha>
106
106
  ```
107
107
 
package/bin/create.mjs CHANGED
@@ -8,9 +8,9 @@ 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 = "yassine-ahmed/clubedge-starter";
12
- const defaultStarterRef = "v0.1.0";
13
- const defaultStarterCommit = "4334121e4ce46a331d7c542c6025fdfe2b8c0657";
11
+ const starterRepository = "Clubedge/clubedge-starter";
12
+ const defaultStarterRef = "v0.1.1";
13
+ const defaultStarterCommit = "0be0c18d41f01cd011c576fb65c25711081b8ad4";
14
14
  const packageVersion = JSON.parse(
15
15
  await readFile(new URL("../package.json", import.meta.url), "utf8"),
16
16
  ).version;
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@clubedge/create-clubedge-app",
3
- "version": "0.1.5",
3
+ "version": "0.1.10",
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",
@@ -20,11 +20,11 @@
20
20
  "license": "Apache-2.0",
21
21
  "repository": {
22
22
  "type": "git",
23
- "url": "https://github.com/yassine-ahmed/create-clubedge-app.git"
23
+ "url": "https://github.com/Clubedge/create-clubedge-app.git"
24
24
  },
25
- "homepage": "https://github.com/yassine-ahmed/create-clubedge-app#readme",
25
+ "homepage": "https://github.com/Clubedge/create-clubedge-app#readme",
26
26
  "bugs": {
27
- "url": "https://github.com/yassine-ahmed/create-clubedge-app/issues"
27
+ "url": "https://github.com/Clubedge/create-clubedge-app/issues"
28
28
  },
29
29
  "keywords": [
30
30
  "create-clubedge-app",