Skip to content

ci: fail when uv.lock no longer matches pyproject.toml #14

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tactino merged 1 commit into from
Sep 29, 2026
Merged

ci: fail when uv.lock no longer matches pyproject.toml #14

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,12 @@ jobs:
with:
enable-cache: true

# `--frozen` below installs from uv.lock without asking whether it still
# matches pyproject.toml. It did not, for a while: robomimic moved to
# 0.4.0 and the lock kept 0.3.0. This fails when the two disagree.
- name: Lock is current
run: uv lock --check

# No extras: the point of this package is that it installs without a
# deep learning stack, and the test suite asserts exactly that.
- name: Sync
Expand Down
Loading