Skip to content

chore: update devbox.lock files across all projects#2870

Open
mikeland73 wants to merge 2 commits into
mainfrom
claude/great-babbage-y2sguj
Open

chore: update devbox.lock files across all projects#2870
mikeland73 wants to merge 2 commits into
mainfrom
claude/great-babbage-y2sguj

Conversation

@mikeland73

Copy link
Copy Markdown
Collaborator

What

Refreshes devbox.lock files across the root project and all example projects by running devbox update in each project, followed by devbox update --sync-lock from the root to sync shared dependencies.

65 lock files updated, no devbox.json changes.

Notable version bumps

  • nixpkgs (nixpkgs-unstable) advanced to the latest commit
  • go 1.26.1 → 1.26.3
  • git 2.53.0 → 2.54.0
  • nodejs_18 18.19.1 → 18.20.8
  • python310 3.10.13 → 3.10.19
  • minikube 1.32.0 → 1.38.1
  • wget 1.21.4 → 1.25.0
  • …and many more across the example stacks (databases, servers, language toolchains, data science).

Left unchanged

Two external flake references could not be re-resolved in this environment because resolving a branch/tag/HEAD goes through the unauthenticated GitHub API, which is rate-limited here:

  • github:ggerganov/llama.cpp (data_science/llama)
  • github:F1bonacc1/process-compose/v0.43.1 (flakes/remote)

Their devbox.lock entries are empty objects ({}) and are resolved by Nix at build time, so leaving them unchanged has no effect on the lock contents. All other packages in those projects were updated.

Validation

  • All 65 changed lock files are valid JSON.
  • Each project's devbox update completed with exit code 0.

https://claude.ai/code/session_01HobHrYdKYZhSyb5bbgaVXb


Generated by Claude Code

Ran `devbox update` across the root project and all example projects,
followed by `devbox update --sync-lock` to sync shared dependencies.

This bumps nixpkgs (nixpkgs-unstable) and pinned package versions to
their latest resolved revisions. Notable bumps include go 1.26.1->1.26.3,
git 2.53.0->2.54.0, nodejs 18.19.1->18.20.8, python 3.10.13->3.10.19,
minikube 1.32.0->1.38.1, wget 1.21.4->1.25.0, among others.

The external flake refs `github:ggerganov/llama.cpp` and
`github:F1bonacc1/process-compose/v0.43.1` were left unchanged (their
devbox.lock entries are empty and resolved by nix at build time).

https://claude.ai/code/session_01HobHrYdKYZhSyb5bbgaVXb
Copilot AI review requested due to automatic review settings June 15, 2026 05:08

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review any files in this pull request.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

The nixpkgs-unstable bump upgraded several language toolchains to
versions incompatible with these examples' source/config, causing
TestExamples failures in CI. Reverting these specific lock files to
their previous (working) state while keeping the other 54 updated:

- zig/zig-hello-world: zig 0.16 removed the `root_source_file` build API
- nodejs/nodejs-yarn, nodejs/nodejs-pnpm: yarn/pnpm no longer on PATH
- csharp, fsharp: only dotnet-sdk 8.x available; projects target net6.0
- java/gradle, java/maven: JDK toolchain bump
- elixir/elixir_hello: newer OTP TLS rejects builds.hex.pm certificate
- python/poetry/poetry-pyproject-subdir: python/poetry bump
- stacks/rails, stacks/jekyll: ruby toolchain bump

These breakages are upstream-version incompatibilities with no
lock-level fix other than reverting the affected example.

https://claude.ai/code/session_01HobHrYdKYZhSyb5bbgaVXb
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants