Regenerate requirements.txt from uv.lock

[VishnuR23]

Problem

requirements.txt is generated from uv.lock by the export-requirements pre-commit hook. It has drifted, and the drift landed on the worst possible line:

source	datasets
pyproject.toml	>=4.8.4,<5
uv.lock	4.8.5
requirements.txt	4.5.0

So the file both lags the lock and pins a version pyproject.toml explicitly forbids.

4.5.0 is the exact version #1867 existed to escape. From its changelog entry:

datasets 4.5.0 does an unguarded from torchvision.io import VideoReader whenever torchvision is already imported, and torchvision 0.26 (required by torch 2.11 stacks) removed it, so every dataset.set_format("pt") raised ImportError — in one case killing an 11.5h tokenization job at its final step.

#1867 changed CHANGELOG.md, pyproject.toml and uv.lock, but not requirements.txt:

$ git show --name-only b9269782a
CHANGELOG.md
pyproject.toml
uv.lock

Anyone installing from requirements.txt therefore gets the broken version the fix was about.

Change

Regenerated with the hook's exact command from .pre-commit-config.yaml:

uv export --format requirements-txt --no-hashes --all-extras \
  --group cuda12 --no-emit-project --output-file requirements.txt

That changes exactly one line. I re-ran the export against the result and it is a no-op, so this is the file's correct generated state and there is no other drift hiding in it.

Why it went unnoticed

The hook is declared with files: ^uv\.lock$, so it fires only for contributors who have pre-commit installed locally. CI (pr_checks.yml) runs make style-check and make quality-check; neither regenerates this file. So a uv.lock change can land with requirements.txt untouched and nothing complains.

That enforcement gap affects other hooks too — main currently also violates the ban-keywords hook — so I filed it separately as #1906 rather than bundling a CI change into this fix. This PR is just the regenerated artifact.

Testing

• Re-running the export is a no-op (idempotent).
• The single changed line now satisfies pyproject.toml's datasets>=4.8.4,<5.

Generated file only; no files under open_instruct/, so the CHANGELOG check does not apply and no GPU code paths are touched.

GPU_TESTS=bypass

🤖 Generated with Claude Code