Conversation
updates: - [github.com/crate-ci/typos: v1.45.1 → v1](crate-ci/typos@v1.45.1...v1) - [github.com/lycheeverse/lychee: lychee-v0.23.0 → nightly](lycheeverse/lychee@lychee-v0.23.0...nightly)
The autoupdate suggested mutable refs (typos `v1`, lychee `nightly`). The existing comment on the typos entry already documents that mutable `v1` must be replaced manually; pinning to the concrete tag `v1` currently points to (`v1.45.2`) keeps the build reproducible. Reverting the lychee change keeps it on the same pinned release that was in main before. Co-Authored-By: Claude <noreply@anthropic.com>
worktrunk-bot
left a comment
worktrunk-bot
left a comment
There was a problem hiding this comment.
Pushed a follow-up commit pinning to concrete versions: typos to v1.45.2 (what v1 currently resolves to) and lychee back to lychee-v0.23.0. The comment above the typos entry already documents the manual-pinning policy, and nightly is a moving branch on lychee — both refs would have made the build non-reproducible. If a lychee bump is desired separately, lychee-v0.24.1 (2026-04-24) is the latest concrete release.
|
@worktrunk-bot fix the failure in another PR |
|
Investigated — the macOS failure is unrelated to this PR's pre-commit pin. Opened #2440 to pin nushell to |
## Summary - The `version: '*'` specifier in `hustcer/setup-nu@v3` started failing on macOS arm64 around 2026-04-27 16:48Z with `No release for Nushell matching version specifier * of default feature`. The action SHA was unchanged, so this is an upstream regression in the wildcard resolution path. - Earlier successful runs (e.g. [25003041167](https://github.com/max-sixty/worktrunk/actions/runs/25003041167)) resolved `*` to `0.112.2`, so pinning to that version restores the previous behavior and makes the build reproducible. - Same pinning philosophy as a985e24 (pre-commit hook revs) — concrete versions over moving refs. Fixes the failing `test (macos)` check on #2438 and on `main`. ## Test plan - [ ] `test (linux)` passes - [ ] `test (macos)` passes — the previously failing job - [ ] `test (windows)` passes (nushell step is skipped on Windows; unaffected) - [ ] `code-coverage` and `benchmarks` jobs still install nushell successfully Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com>
2 participants
updates: