ci: tighten install-path comments
Collapse the worked-example narrative to one-line WHYs. Code is unchanged.
This commit is contained in:
parent
2f1d2deb5c
commit
75a8129e3b
5 changed files with 14 additions and 42 deletions
14
.github/workflows/release-desktop.yml
vendored
14
.github/workflows/release-desktop.yml
vendored
|
|
@ -443,16 +443,10 @@ jobs:
|
|||
|
||||
- name: Install frontend dependencies
|
||||
working-directory: studio/frontend
|
||||
# `npm ci` so a release build can never pull a fresh minor/patch
|
||||
# of a transitive dep from the registry via caret-range resolution;
|
||||
# the tree is exactly what the committed lockfile pins.
|
||||
#
|
||||
# Lifecycle scripts (esbuild native-binary postinstall, etc.) are
|
||||
# required for `vite build`. The pre-install lockfile structural
|
||||
# audit (lockfile_supply_chain_audit.py) is the practical defence
|
||||
# against the npm postinstall-dropper class -- it fires BEFORE any
|
||||
# tarball runs, on the injection pattern itself rather than an
|
||||
# advisory-DB lookup.
|
||||
# npm ci: release build installs exactly what the lockfile pins.
|
||||
# Lifecycle scripts (esbuild native-binary postinstall) are required
|
||||
# for vite build; lockfile_supply_chain_audit.py runs pre-install as
|
||||
# the defence against the postinstall-dropper class.
|
||||
run: npm ci --no-fund --no-audit
|
||||
|
||||
# ── Rust ──
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue