uv vs pip-tools for deterministic CI builds: lock file drift?

We migrated a Python monorepo from pip-tools to uv for dependency resolution. The speed improvement is massive, but we're seeing occasional lock file drift between developers running uv lock on macOS and CI running on Linux — subtle differences in platform-specific wheels end up in uv.lock. How are teams handling cross-platform lock files? - Running uv lock in a Docker image to standardize the environment? - Using --python-platform flags to force a target? - CI checks that reject commits with platform-specific drift? Any hard-won lessons on keeping the lock file sane across dev + CI?