[renovate]

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[GraemeF]

Held until 2026-10-26 16:36 UTC.

This lock refresh moves one input. The root nixpkgs input (nixos-unstable) goes from 02c087f3fe67 to 3ec636362e18, and 3ec636362e18 was committed on 2026-10-23 16:35 UTC. That is under 3 days old. No other input moves, and no hash elsewhere in the repo is computed from this lock.

A trim would pin nixpkgs back to the newest nixos-unstable channel release that is at least 3 days old. The channel's release history goes straight from 02c087f3fe67, which main already holds, to 3ec636362e18. So a trim would leave the branch with no change from main, and there is nothing to take yet.

The hold ends when 3ec636362e18 turns 3 days old. Then the refresh gets a full review as it stands at that point, including the devshell tools that move with nixpkgs. Both required checks are green on the current head.

[GraemeF]

Review after the hold ended.

This lock refresh still moves only the root nixpkgs input (nixos-unstable), from 02c087f3fe67 to 3ec636362e18. That revision was committed on 2026-10-23 16:35 UTC, so it is now over 3 days old and the trim has nothing to pin back. No other input moves.

No package the flake takes from nixpkgs changes version between the two revisions. I evaluated each one at both revisions: bash 5.3p20, coreutils 9.12, gawk 5.4.1, git 2.56.0, herdr 0.9.5, jq 1.8.2 and shellcheck 0.11.0. bd comes from the beads input, which this refresh does not touch. No file in the repo holds a hash computed from this lock.

The update is safe to take. It merges once the branch is up to date with main and both required checks are green on that head.