Repository navigation
Keep the Pi's lockfile from blocking updates - #74
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
On the Pi,
npm installrewritespackage-lock.json. The nextgit pull(and the hourlyscripts/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.shdiscards changes topackage-lock.jsonbefore merging, and installs withnpm ci, which installs from the lockfile without touching it.npm ciand say how to undo a rewritten lockfile.🤖 Generated with Claude Code