sync-deps
Regenerate deps-lock.json after changing deps.edn
SKILL.md.claude/skills/sync-deps/SKILL.md
GitHubSync Dependencies Lock File
Regenerate deps-lock.json after changing deps.edn.
Background
The uberjar build consumes deps-lock.json (a clj-nix lock file, wired in as a
flake input) to cache Maven/Clojure dependencies. When deps.edn changes, the
lock file must be regenerated or the uberjar build resolves stale dependencies.
Process
Run:
just deps-lockCheck the result:
git diff --stat deps-lock.jsonAn unchanged lock file is fine — it means the resolved artifact set did not change (e.g. a dependency was promoted from transitive to explicit at the same version).
If the lock file changed, verify the uberjar still builds:
nix build .#bits-uberjarCommit
deps.ednanddeps-lock.jsontogether.
$ARGUMENTS