You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+10-2Lines changed: 10 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ The decision was made to allow faster iterations and to keep features parity in
26
26
## Technologies
27
27
28
28
- Node v24.14 (a `.nvmrc` is presented for [nvm](https://github.com/nvm-sh/nvm) users).
29
-
-[pnpm](https://pnpm.io/workspaces) for managing the monorepo and dependencies.
29
+
-[pnpm](https://pnpm.io/workspaces)10.33.4 for managing the monorepo and dependencies.
30
30
31
31
## Projects
32
32
@@ -87,10 +87,18 @@ We would appreciate if you dedicate the time and read them carefully:
87
87
After cloning the project, please make sure to run the following commands to bootstrap the project:
88
88
89
89
```bash
90
-
npm i -g pnpm@9.14.4
90
+
nvm use
91
+
corepack enable
92
+
corepack prepare pnpm@10.33.4 --activate
91
93
pnpm install
92
94
```
93
95
96
+
## Dependency Supply-Chain Hardening
97
+
98
+
This repo delays newly published package versions for seven days via `minimumReleaseAge: 10080` in `pnpm-workspace.yaml`. Keep using the pinned pnpm version from `package.json`; older pnpm versions do not enforce this setting.
99
+
100
+
Keep `pnpm-lock.yaml` committed, use frozen-lockfile installs in CI, and avoid adding git or tarball dependencies unless they are reviewed explicitly. If an urgent dependency update must bypass the cooldown, add a temporary `minimumReleaseAgeExclude` entry in `pnpm-workspace.yaml`, review the package contents/provenance first, and remove the exception after the release ages out.
0 commit comments