Migrate from rye to uv (eMudhra CA response)
Merged
MI
1mo ago+1979+1979+0123456789012345678901234567890123456789-610-610-012345678901234567890123456789
Why
- Astral has deprecated rye in favour of uv, and rye can no longer be installed in our environments.
- The rye lockfiles pinned
certifi==2025.4.26, which still ships the emSign ECC Root CA - G3.certifi2026.10.19 removes that root as part of the eMudhra CA response. - The rest of the org already runs uv 0.13.4. That release bundles the updated Mozilla root store (GHSA-hq85-5cpj-mr62).
What changed
pyproject.toml: replaced[tool.rye](managed = true, emptydev-dependencies) with[tool.uv]andrequired-version = ">=0.13.4". The hatchling build backend is unchanged.uv.lockreplacesrequirements.lockandrequirements-dev.lock, which were identical. Both rye lockfiles are deleted.Makefile:check_ryeis nowcheck_uv, which enforcesMIN_UV_VERSION=0.13.4using the same pattern as MCP-Template.rye run/rye syncare nowuv run/uv sync. Therequirementstarget now runsuv exportinstead of copying the deleted lockfile.- CI (
test_target_tests.yaml,vulture_dead_code.yaml):eifinger/setup-rye@v4(versionlatest) is replaced byastral-sh/setup-uv@v7pinned to0.13.4with caching, andrye syncis nowuv sync. README.md,tests/README.mdand.cursorrulesnow give uv install and usage instructions.
Dependency versions
The lock was resolved using the old pins as constraints, then re-locked without them, so every previously pinned version is kept. The only intended change is certifi.
| Package | Old | New |
|---|---|---|
| certifi | 2025.4.26 | 2026.10.19 |
| colorama | (not locked) | 0.4.6, win32 only |
| win32-setctime | (not locked) | 1.2.0, win32 only |
| greenlet | (not locked) | 3.5.6, platform-marker dep of sqlalchemy |
The three new entries appear because uv.lock is universal and rye's lock was platform-specific. They are not upgrades.
Verification
uv syncanduv lock --checkpass, andcertifi.__version__reports2026.10.19.make testpasses (1 passed) with dummy values for the env vars CI supplies through secrets. The same result occurs on the old rye-pinned versions in a throwaway venv.make vultureis clean.black --checkreports no changes.make requirementsproduces arequirements.txtwithcertifi==2026.10.19.make check_uvpasses with uv 0.13.4 and fails with a clear message when a stub reports uv 0.9.2.grep -rni ryereturns nothing.
Not verified / known issues
- The CI workflows were not run locally. They will run on this PR.
make fmtprintsfind: expected an expression between '-o' and ')'from its JSON-formatting step. This bug exists before this PR: theIGNORE_LINT_DIRSpattern expansion is malformed. It was unreachable before because rye was not installed. It is out of scope here and left unchanged.
Generated by Claude Code
Summary by cubic
Migrates the project from rye to uv so the lockfile resolves to certifi 2026.10.19, which drops the compromised emSign ECC Root CA - G3. The rye lockfiles pinned certifi==2025.4.26, and uv 0.13.4 is required because it bundles the updated Mozilla root store (GHSA-hq85-5cpj-mr62).
- Replaces
[tool.rye]with[tool.uv](required-version = ">=0.13.4");uv.lockreplaces both identical rye lockfiles, andmake requirementsnow usesuv export. - Makefile and CI switch
rye run/rye synctouv run/uv sync;check_ryebecomescheck_uvenforcing uv ≥ 0.13.4, and CI usesastral-sh/setup-uv@v7pinned to 0.13.4 with caching. - CI drops
setup-pythonand lets uv provision the interpreter from.python-version, then runsuv sync --lockedto verify the committed lockfile. - README, tests/README, and .cursorrules now document uv.
Dependencies
- All previously pinned versions are kept; the only intended change is
certifi2025.4.26 → 2026.10.19. colorama,win32-setctime, andgreenletappear inuv.lockbecause it is universal, not because they were added.