fix(examples/jekyll): pin ruby@3.1 back to 3.1.4 for macOS

[mikeland73]

Summary

Fixes the nightly cli-tests failure in stacks_jekyll_run_test on macOS (e.g. run 35838473204), failing every scheduled run since #2974. That PR bumped ruby@3.1 to 3.1.7 (nixpkgs/bce5fe2b#ruby_3_1), whose aarch64-darwin build lacks the socket extension, so gem install fails with uninitialized constant Gem::Commands::InstallCommand (masking LoadError: cannot load such file -- socket). This restores the previous 3.1.4 lock entry, same as #2974 did for libffi and stack; #2974's own CI missed it because macOS only runs on schedule or with run-mac-tests.

How was it tested?

Locally on arm64 macOS: DEVBOX_RUN_PROJECT_TESTS=1 go test ./testscripts -run TestExamples/stacks_jekyll_run_test passes with this change and fails with the same error on the current main lockfile.

Community Contribution License

All community contributions in this pull request are licensed to the project
maintainers under the terms of the
Apache 2 License.

By creating this pull request, I represent that I have the right to license the
contributions to the project maintainers under the Apache 2 License as stated in
the
Community Contribution License.

🤖 Generated with Claude Code

[mikeland73]

@claude ptal

[claude]

Claude finished @mikeland73's task in 1m 1s —— View job

---

Review: PR #2984

• Gather context (PR diff, lockfile changes, related PR chore(deps): update devbox packages across all projects #2974)
• Review the devbox.lock changes for correctness
• Check CLAUDE.md for repo conventions (none apply here — no root CLAUDE.md found)
• Post review feedback

LGTM. The fix is a clean, well-scoped lockfile-only change:

• examples/stacks/jekyll/devbox.lock:152-157 reverts ruby@3.1's resolution from nixpkgs rev bce5fe2b... (v3.1.7) back to 10b81304... (v3.1.4), matching the last_modified/resolved/version/store-path fields consistently across all four platforms (aarch64-darwin, aarch64-linux, x86_64-darwin, x86_64-linux).
• This mirrors exactly how chore(deps): update devbox packages across all projects #2974 pinned libffi@latest to an older nixpkgs revision (98b00b69..., Feb 2024) in the same lockfile — good precedent, and the new ruby revision (2024-02-10) lines up with that same era, which is reassuring for consistency.
• devbox.json still declares "ruby@3.1" (a version range), so no change is needed there — the lockfile is the right place to pin the exact resolved build. This is correct.
• Root cause explanation (aarch64-darwin 3.1.7 build missing the socket extension, masked by a confusing Gem::Commands::InstallCommand error) is plausible and consistent with known nixpkgs ruby packaging regressions.
• Scope is minimal — single file, no unrelated changes.

I can't independently verify the Nix store hashes/build outputs in this sandbox (no nix available here, and this only reproduces on aarch64-darwin per the nightly schedule), but the diff's internal structure is self-consistent and the author confirmed local testing on arm64 macOS reproduces the failure on main and passes with this change — that's the right verification method for this kind of fix.

No changes requested.