Nix Update
Goal
Update this repository's Nix flake inputs and summarize important package version changes.
Success means flake.lock is updated, relevant packages are compared where possible, verification commands pass or failures are clearly reported, and the user knows how to install the updated profile.
Stop when the update is verified or the lockfile is restored after a failed update.
Workflow
- Inspect the current state:
git status --short
git diff -- flake.lock
git rev-parse HEAD:flake.lock >/dev/null 2>&1 && git show HEAD:flake.lock | rg '"rev"'
- Capture the current nixpkgs commit from
flake.lock.
- Run the repo update command:
make update
- Capture the new nixpkgs commit from
flake.lock.
- Read
flake.nix and compare versions only for packages that are actually present.
- Verify the update:
make test-pre
nix build .#default --dry-run
- If verification fails because of the update, explain the failure and recommend reverting
flake.lock. Do not revert user changes unless the user asks.
Packages To Compare When Present
- Version control:
git, gh, lazygit.
- Languages:
rustup, go, python3, deno, bun.
- Shell and terminal:
fish, zsh, tmux, starship, zellij.
- CLI tools:
ripgrep, fd, bat, eza, delta, fzf, jq, yq.
- Editors and agents:
neovim, codex, claude-code.
- Dev tools:
direnv, nix-direnv.
- Containers:
docker-client, docker-compose, lazydocker, k9s.
- System tools:
htop, btop, ncdu.
- Other tools:
just, buf, grpcurl, dogdns.
Use this form for version checks:
nix eval "github:NixOS/nixpkgs/<commit>#<package>.version" --raw
If a package cannot be evaluated, mark it N/A and continue.
Version Summary
Report:
## Flake Update
- nixpkgs: `<old>` -> `<new>`
- Compare: https://github.com/NixOS/nixpkgs/compare/<old>..<new>
## Package Updates
| Package | Old | New | Notes |
| --- | --- | --- | --- |
| git | 2.x | 2.y | patch |
## Verification
- `make test-pre`: pass/fail
- `nix build .#default --dry-run`: pass/fail
## Next Steps
- Review and commit `flake.lock`.
- Install the updated packages with `make profile` (or `./bootstrap.sh profile`).
Constraints
- Keep output concise and actionable.
- Run independent version comparisons in parallel when practical.
- Do not compare packages that are not in
flake.nix.
- Do not imply that updating
flake.lock updates the installed profile.
- Preserve unrelated working tree changes.
1---2name: nix-update3description: Update this dotfiles flake.lock, compare key Nix package versions, verify the update, and summarize changed packages. Use for Nix flake maintenance in this repo.4---56# Nix Update78## Goal910Update this repository's Nix flake inputs and summarize important package version changes.1112Success means `flake.lock` is updated, relevant packages are compared where possible, verification commands pass or failures are clearly reported, and the user knows how to install the updated profile.1314Stop when the update is verified or the lockfile is restored after a failed update.1516## Workflow17181. Inspect the current state:1920```bash21git status --short22git diff -- flake.lock23git rev-parse HEAD:flake.lock >/dev/null 2>&1 && git show HEAD:flake.lock | rg '"rev"'24```25262. Capture the current nixpkgs commit from `flake.lock`.273. Run the repo update command:2829```bash30make update31```32334. Capture the new nixpkgs commit from `flake.lock`.345. Read `flake.nix` and compare versions only for packages that are actually present.356. Verify the update:3637```bash38make test-pre39nix build .#default --dry-run40```41427. If verification fails because of the update, explain the failure and recommend reverting `flake.lock`. Do not revert user changes unless the user asks.4344## Packages To Compare When Present4546- Version control: `git`, `gh`, `lazygit`.47- Languages: `rustup`, `go`, `python3`, `deno`, `bun`.48- Shell and terminal: `fish`, `zsh`, `tmux`, `starship`, `zellij`.49- CLI tools: `ripgrep`, `fd`, `bat`, `eza`, `delta`, `fzf`, `jq`, `yq`.50- Editors and agents: `neovim`, `codex`, `claude-code`.51- Dev tools: `direnv`, `nix-direnv`.52- Containers: `docker-client`, `docker-compose`, `lazydocker`, `k9s`.53- System tools: `htop`, `btop`, `ncdu`.54- Other tools: `just`, `buf`, `grpcurl`, `dogdns`.5556Use this form for version checks:5758```bash59nix eval "github:NixOS/nixpkgs/<commit>#<package>.version" --raw60```6162If a package cannot be evaluated, mark it `N/A` and continue.6364## Version Summary6566Report:6768```markdown69## Flake Update7071- nixpkgs: `<old>` -> `<new>`72- Compare: https://github.com/NixOS/nixpkgs/compare/<old>..<new>7374## Package Updates7576| Package | Old | New | Notes |77| --- | --- | --- | --- |78| git | 2.x | 2.y | patch |7980## Verification8182- `make test-pre`: pass/fail83- `nix build .#default --dry-run`: pass/fail8485## Next Steps8687- Review and commit `flake.lock`.88- Install the updated packages with `make profile` (or `./bootstrap.sh profile`).89```9091## Constraints9293- Keep output concise and actionable.94- Run independent version comparisons in parallel when practical.95- Do not compare packages that are not in `flake.nix`.96- Do not imply that updating `flake.lock` updates the installed profile.97- Preserve unrelated working tree changes.
wcygan