Upgrade pydantic to 2.14.1 with a recompiled requirements-dev.txt

Abierto
#6,373 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
15/100
Tipo de issue
Refactorización
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
python
Área
backend

Línea de trabajo

The body says the issue is not open for contribution, so confirm that with maintainers before starting. The work touches requirements.in, requirements.txt and requirements-dev.txt, which must be recompiled with uv pip compile so typing-extensions agrees. Check the QTI models under contentcuration/contentcuration/utils/assessment/qti/ and run the tests in contentcuration/contentcuration/tests/utils/qti/. Done means uv pip sync succeeds and the pinned versions match.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

dependencies DEV: backend python

❌ This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.

Overview

Dependabot PR #6371 bumped pydantic from 2.13.4 to 2.14.1, but its dependency install failed and it was closed unmerged. That PR regenerated only requirements.txt. requirements-dev.txt still pins the old typing-extensions, so the two lock files conflict.

Complexity: Low
Target branch: unstable

Context
  • requirements-dev.in starts with -c requirements.txt, so requirements-dev.txt must match requirements.txt on every package they share. Dependabot regenerates only requirements.txt.
  • These four packages move together in requirements.txt, so they have to be upgraded as a set:
    • pydantic 2.13.4 → 2.14.1
    • pydantic-core 2.46.4 → 2.50.1 (pydantic pins it exactly)
    • typing-extensions 4.15.0 → 4.16.0
    • typing-inspection 0.4.2 → 0.4.4
  • requirements-dev.txt pins typing-extensions==4.15.0 (via exceptiongroup, virtualenv), which conflicts with the 4.16.0 that requirements.txt needs.
  • pydantic is a production dependency. The QTI models in contentcuration/contentcuration/utils/assessment/qti/ are built on it, and publishing converts exercises to QTI with them.
  • The 2.14 release lists two behaviour changes that can affect those models:
    • Enum constructors now run in both validation modes. Enum-typed fields are in constants.py, mathml/fields.py and html/*.py.
    • model_config is no longer mutated. XMLElement in base.py sets extra="forbid", validate_assignment=True and frozen=True.
  • The 2.14 security advisories (GHSA-gj4f-r7mf-jjxh, Fraction exponents; GHSA-955g-x97g-8mcp, multi-host URLs) don't affect Studio. Its pydantic models use no Fraction and no multi-host URL types.
The Change
  • requirements.in should pin pydantic==2.14.1.
  • requirements.txt and requirements-dev.txt should both be recompiled with uv pip compile (the command is in each file's header), so they agree on typing-extensions and every other shared package.
Acceptance Criteria
  • uv pip sync requirements.txt requirements-dev.txt succeeds on Python 3.10.
  • requirements.txt pins pydantic==2.14.1, pydantic-core==2.50.1, typing-extensions==4.16.0 and typing-inspection==0.4.4.
  • requirements-dev.txt pins the same typing-extensions version as requirements.txt.
  • pytest contentcuration/contentcuration/tests/utils/qti/ passes.
  • The full Python CI job runs and passes.
References

AI usage

rtibblesbot (Claude Code) reviewed #6371, recommended closing it, and drafted this issue from that review and the lock files.

Filed from #6371's review.

Lenguaje dominante
Python
Estrellas
212
Forks
321
Merge medio
1 d 7 h
PR fusionados (30 d)
14

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de learningequality/studio

Todos los issues de learningequality/studio

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.