Skip to content

chore: sync uv.lock with the numba>=0.57 pin from #340#343

Merged
lstein merged 1 commit into
masterfrom
lstein/chore/lock-numba-pin
Jul 5, 2026
Merged

chore: sync uv.lock with the numba>=0.57 pin from #340#343
lstein merged 1 commit into
masterfrom
lstein/chore/lock-numba-pin

Conversation

@lstein

@lstein lstein commented Jul 5, 2026

Copy link
Copy Markdown
Owner

Summary

Commit 93b5f4f (#340) added the numba>=0.57 pin to pyproject.toml but didn't regenerate uv.lock, so the lockfile has been out of sync with the project metadata ever since — every uv sync re-derives the two missing lines and leaves uv.lock dirty in the working tree (this bit us three times in one session while working on #342).

Regenerated with uv lock. The diff is exactly the two lines recording the pin; no dependency versions change.

Test plan

  • uv lock --check passes (it fails on master).
  • No resolution changes — 151 packages resolve identically.

🤖 Generated with Claude Code

The pin was added to pyproject.toml in 93b5f4f without regenerating the
lockfile, so every `uv sync` since has dirtied uv.lock in the working
tree. Regenerated with `uv lock`; `uv lock --check` now passes.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@lstein lstein merged commit 111e3b4 into master Jul 5, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant