Skip to content

Keep the Pi's lockfile from blocking updates - #74

Merged
lolman420 merged 1 commit into
masterfrom
update-pi-lockfile
Nov 12, 2026
Merged

lolman420 merged 1 commit into
masterfrom
update-pi-lockfile

Conversation

@lolman420

Copy link
Copy Markdown
Contributor

Why

On the Pi, npm install rewrites package-lock.json. The next git pull (and the hourly scripts/update-pi.sh, which merges with --ff-only) then refuses to update because of the "local changes", so the Pi silently stays on an old version. This just happened: the Pi was stuck on 2.1.0 while master was 2.2.

What changed

  • scripts/update-pi.sh discards changes to package-lock.json before merging, and installs with npm ci, which installs from the lockfile without touching it.
  • The README's deploy steps use npm ci and say how to undo a rewritten lockfile.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@lolman420
lolman420 merged commit a990e1c into master Nov 12, 2026
1 check passed
@lolman420
lolman420 deleted the update-pi-lockfile branch November 12, 2026 10:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant