cabloy 5.1.88 → 5.1.89

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
@@ -1,5 +1,11 @@
1
1
  # Changelog
2
2
 
3
+ ## 5.1.89
4
+
5
+ ### Improvements
6
+
7
+ - Document the `pnpm` `minimumReleaseAge` workaround.
8
+
3
9
  ## 5.1.88
4
10
 
5
11
  ### Features
package/README.md CHANGED
@@ -55,6 +55,33 @@ npm create cabloy
55
55
 
56
56
  The generated project already includes `CLAUDE.md` and the `.claude/` workspace assets. This path creates a Cabloy Basic project baseline. Open this project in Claude Code and start coding immediately with project-specific guidance.
57
57
 
58
+ #### pnpm 11 supply-chain protection note
59
+
60
+ `pnpm` 11 enables the `minimumReleaseAge` supply-chain protection by default. Newly published packages may be blocked for a short time window before `pnpm` allows installation.
61
+
62
+ This matters for `npm create cabloy` because the command downloads Cabloy from npm and then automatically runs `npm run init`. If your environment blocks newly published packages during that flow, temporarily set `pnpm_config_minimum_release_age=0` for the current shell session and rerun the command.
63
+
64
+ **Windows PowerShell**
65
+
66
+ ```powershell
67
+ $env:pnpm_config_minimum_release_age = "0"
68
+ npm create cabloy
69
+ ```
70
+
71
+ **Windows Command Prompt**
72
+
73
+ ```cmd
74
+ set pnpm_config_minimum_release_age=0 && npm create cabloy
75
+ ```
76
+
77
+ **macOS / Linux**
78
+
79
+ ```bash
80
+ pnpm_config_minimum_release_age=0 npm create cabloy
81
+ ```
82
+
83
+ If you already created the project directory and only need to rerun initialization, use the same environment variable with `npm run init`.
84
+
58
85
  For **Cabloy Start**, purchase access to the licensed private repository, clone `git@github.com:cabloy/cabloy-start.git`, and run `npm run init`. For the complete Start onboarding flow, read the [Cabloy Start](https://docs.cabloy.com/editions/cabloy-start) page.
59
86
 
60
87
  Then continue with the framework docs:
@@ -26,6 +26,33 @@ npm create cabloy
26
26
 
27
27
  The generated project already includes `CLAUDE.md` and the `.claude/` workspace assets. This path creates a Cabloy Basic project baseline. Open this project in Claude Code and start coding immediately with project-specific guidance.
28
28
 
29
+ ### pnpm 11 supply-chain protection note
30
+
31
+ `pnpm` 11 enables the `minimumReleaseAge` supply-chain protection by default. Newly published packages may be blocked for a short time window before `pnpm` allows installation.
32
+
33
+ This matters for `npm create cabloy` because the command downloads Cabloy from npm and then automatically runs `npm run init`. If your environment blocks newly published packages during that flow, temporarily set `pnpm_config_minimum_release_age=0` for the current shell session and rerun the command.
34
+
35
+ #### Windows PowerShell
36
+
37
+ ```powershell
38
+ $env:pnpm_config_minimum_release_age = "0"
39
+ npm create cabloy
40
+ ```
41
+
42
+ #### Windows Command Prompt
43
+
44
+ ```cmd
45
+ set pnpm_config_minimum_release_age=0 && npm create cabloy
46
+ ```
47
+
48
+ #### macOS / Linux
49
+
50
+ ```bash
51
+ pnpm_config_minimum_release_age=0 npm create cabloy
52
+ ```
53
+
54
+ If you already created the project directory and only need to rerun initialization, use the same environment variable with `npm run init`.
55
+
29
56
  ## 3. Start the backend
30
57
 
31
58
  ```bash
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "cabloy",
3
- "version": "5.1.88",
3
+ "version": "5.1.89",
4
4
  "gitHead": "2c5c19284bab738e492856189acb6fad74b8a7b7",
5
5
  "description": "A Node.js fullstack framework",
6
6
  "keywords": [