Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Register and check rules for using, installing, testing and relocking from uv.lock

Abierto
  • ¿Algo no está bien?
#3,996 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 3 días

@anth-volk ya está trabajando en esto.

Desde el 21/10/2026.

  • #3997 de @anth-volk — abierto

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
docker, github-actions, python
Área
ci-cd, testing, tooling

Línea de trabajo

Start with rules/registry.toml and inspect the rules added by #3995 and #3994, which this proposal builds on. Trace how registry rules are mechanically checked across workflows, scripts, Makefiles, Dockerfiles, and Modal image definitions. Done means all four rules are registered and checked, with documented exception requirements for installs that cannot yet use the lock.

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

Descripción

Problem

The Cloud Run image installs exactly the versions in uv.lock (uv sync --frozen), but nothing checks that the rest of the repository does the same. A workflow step, script, Makefile target or Dockerfile can still install with pip or an unfrozen uv run, and tests can run against versions production does not run. Nothing checks that uv.lock matches pyproject.toml in pull request CI, or that a scheduled relock exists.

Proposal

Register four mechanically checked rules in rules/registry.toml:

  1. We use uv.lock: every project directory has a committed uv.lock, and pull request CI runs uv lock --check.
  2. We install from uv.lock: every install in workflows, the scripts they run, Makefiles, Dockerfiles and Modal image definitions uses uv sync --frozen / uv run --frozen.
  3. We test from uv.lock: every test command in CI runs through uv run --frozen.
  4. We relock on a schedule: a scheduled workflow relocks every uv.lock with upgrades and opens or updates a pull request.

An install that cannot use the lock yet is a registered exception that names one site, gives a reason, and has a removal condition, or a review date with a tracking issue. A command-line tool pinned with == outside the project may be registered as a pinned-tool.

Builds on #3995 (tests install from uv.lock) and #3994 (daily relock workflow).

Lenguaje dominante
Python
Estrellas
18
Forks
33
Merge medio
2 d 18 h
PR fusionados (30 d)
36

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 PolicyEngine/policyengine-api

Todos los issues de PolicyEngine/policyengine-api

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.