fix(ci): track frontend lockfile for reproducible installs

Browse Source

The blanket package-lock.json gitignore rule meant the frontend lockfile was never committed, so every release installed whatever the registry handed it (silent transitive drift) and setup-node npm caching failed outright with unable to cache dependencies. Scope the ignore rule to the repo root (/package-lock.json; no root package.json exists) and commit the freshly updated frontend lockfile: all deps at max in-range versions (autoprefixer 10.5.6 -> 10.6.0), majors intentionally deferred to the v3 frontend refresh. Verified with a green vite build before committing.

...

This commit is contained in:

John O'Keefe

2026-09-12 22:40:21 -04:00

parent efe45f39e7

commit 2bf8d3887e

2 changed files with 2720 additions and 1 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

frontend/package-lock.json

Generated

+2717

File diff suppressed because it is too large Load Diff