@cellajs/cli 0.4.1 → 0.4.2
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/README.md +16 -1
- package/dist/index.js +231 -80
- package/dist/index.js.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -20,7 +20,7 @@ pnpm cella audit
|
|
|
20
20
|
| `analyze` | Dry run to see what would change on sync. It leaves your files and branches alone but updates git metadata: it fetches upstream and writes `refs/cella/last-sync` and a graft for the sync base |
|
|
21
21
|
| `sync` | Merge upstream changes onto a fresh branch, sync package.json and open a squash-merge PR into `main` |
|
|
22
22
|
| `migrate` | List the upstream migration notes this app has not handled yet, read them, run their codemods, record them |
|
|
23
|
-
| `audit` | Update outdated packages and runtime pins, then rebuild the security overrides from a fresh audit |
|
|
23
|
+
| `audit` | Update outdated packages and runtime pins, then rebuild the security overrides from a fresh audit; report the security fixes this machine's Node, pnpm and gh miss |
|
|
24
24
|
| `stats` | Count files by category and workspace package; with `--since <ref>`, count what the current branch changed, by kind of file |
|
|
25
25
|
| `forks` * | Run normal sync inside local fork repositories |
|
|
26
26
|
| `contributions` * | Pull and adopt changes from local forks |
|
|
@@ -378,6 +378,21 @@ A pin moves within its major, to the newest version older than `minimumReleaseAg
|
|
|
378
378
|
waits until Docker Hub has the `node:<version><suffix>` images the Dockerfiles build from, and the
|
|
379
379
|
audit prints what is left to do on your machine: switching its Node, and building each changed image.
|
|
380
380
|
|
|
381
|
+
### This machine
|
|
382
|
+
|
|
383
|
+
The pins say what the workspace should run; the tools on your machine can still miss security
|
|
384
|
+
fixes. Below the table the audit shows, for each one, what it misses:
|
|
385
|
+
|
|
386
|
+
| Tool | Which one | Feed |
|
|
387
|
+
|------|-----------|------|
|
|
388
|
+
| Node | the one running the audit, which also runs the workspace | nodejs.org release index |
|
|
389
|
+
| pnpm | the one your terminal starts, before it switches to `packageManager` | npm advisory database |
|
|
390
|
+
| gh | the one on your PATH | OSV |
|
|
391
|
+
|
|
392
|
+
A tool that misses a fix gets a dot and the command to fix it, for the way it was installed (Volta,
|
|
393
|
+
Homebrew, or pnpm's own `self-update`), naming the newest version that has every fix and is older
|
|
394
|
+
than `minimumReleaseAge`. The audit does not change these tools itself.
|
|
395
|
+
|
|
381
396
|
### Holding a package back
|
|
382
397
|
|
|
383
398
|
To keep a package off the update list, use pnpm's own setting, with the reason as a comment.
|