This repository was archived by the owner on Jul 24, 2026. It is now read-only.
fix(nix): regenerate npmDepsHash against main's package-lock.json - #105
Merged
schickling merged 1 commit intoJul 20, 2026
Merged
Conversation
PR #104 added the flake with an npmDepsHash computed against the package-lock.json on its own branch. Meanwhile 12a4772 ("sync stale package-lock.json to package.json (0.3.0)") landed on main and changed that lock. The merge of #104 combined the new flake with main's newer lock, so the hash was stale from the moment it landed -- a semantic conflict a text-level merge cannot see. main's Nix workflow has been red on the merge commit (run 29775629348) ever since. Regenerated with the command the flake itself documents: nix run nixpkgs#prefetch-npm-deps -- package-lock.json Verified locally: `nix build .#default` succeeds and `nix flake check` passes all three checks (help, completions, typecheck). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T1xLDkqUDCYUMMADdMqVgP agent-session-id: 312caff5-3274-4d97-baa4-8ff06ab03fc5 agent-tool: Claude Code agent-tool-version: 2.1.215 agent-model: claude-opus-4-8 agent-runtime-profile: /nix/store/acr8a3l2v366jgmwiq8xdrhgz1py0db5-coding-agent-runtime-profile/share/coding-agents/profile.json agent-skills-manifest: /nix/store/sj1v5j91h8v8d1w9lca4040302lwrd6v-agent-skills-corpus/share/agent-skills/manifest.json tooling-profile: dotfiles@unknown-dirty
This was referenced Jul 21, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
What
Regenerate the flake's
npmDepsHashso it matches thepackage-lock.jsonactually onmain.Why
main's Nix workflow has been red since #104 merged, and the cause is a merge-order accident rather than anything wrong with #104 itself:npmDepsHashagainst thepackage-lock.jsonpresent on its own branch.12a4772d("sync stale package-lock.json to package.json (0.3.0)") landed onmainand changed that lock.Run
29775629348(the push build of the #104 merge commit) fails withERROR: npmDepsHash is out of date.How
Regenerated with the command the flake itself documents:
sha256-CfgSssHEdSjL9liKjaw9aYKMtCJdaxWKGbFM59PgNwg=→sha256-FsAjO/CYxyMf30F8ESsxFDI30ckYv1uS4+nkvn9Fl+k=No hand-authored hash: the value is measured from the real lock file.
Verification actually run
Locally, on this branch:
nix build .#default— succeedsnix flake check— passes all three checks:help,completions,typecheckNote
This also unblocks
compoundingtech/convoy, whose own flake takessmalltalkas an input and currently cannot build against a redsmalltalkmain.