Automate label-based Python release versioning with Release Drafter
Los mantenedores suelen responder en 1 día
@imshubham22apr-gif ya está trabajando en esto.
Desde el 10/11/2026.
- #24 de @imshubham22apr-gif — abierto
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 20/100
Línea de trabajo
Read .github/workflows/release.yml, the existing publishing workflow, pyproject.toml, uv.lock, and the release guidance in CONTRIBUTING.md; first trace how a pushed v* tag reaches PyPI publishing. Define how PR labels resolve version bumps and how release creation triggers publishing despite GitHub token event restrictions. Done means the acceptance checks pass, including version and lockfile consistency, preserved publishing checks, and repeat runs without duplicate releases or publications.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Problem / Motivation
PyPI publishing is already automated for pushed v* tags, but preparing a release still requires manually updating the package version and creating a matching tag. There is currently no Release Drafter configuration or workflow to calculate the next version from pull-request labels and maintain release notes.
Current State
pyproject.tomldeclares a static package version (0.1.0)..github/workflows/release.ymlruns on pushedv*tags and rejects tags that do not match the declared package version.CONTRIBUTING.mddocuments manually setting the version and pushing a matching tag.- The existing pipeline builds, verifies, publishes through PyPI Trusted Publishing, and verifies the published package.
Proposed Solution
Use Release Drafter to maintain draft release notes and resolve the next semantic version from labels on merged pull requests. Connect that resolved version to release preparation so package metadata, the lockfile, the GitHub release, and its tag stay consistent without manual version editing. Maintainers should retain control over when a release is published.
Acceptance Criteria
- Add Release Drafter configuration and a workflow that maintains a draft release from merged PRs on the default branch.
- Define and document labels for major, minor, and patch releases; use the highest applicable bump across merged PRs and document the behavior for unlabeled PRs.
- Automatically prepare the resolved package version in
pyproject.tomland keepuv.lockconsistent before building release artifacts. - Ensure the release tag and published Python package version match, using a Python-compatible version format.
- Explicitly connect the release/tag creation mechanism to the publishing pipeline, accounting for GitHub token event-trigger restrictions so an automated release actually starts publishing.
- Preserve the existing build/verification checks, tag/version mismatch guard, and PyPI Trusted Publishing flow.
- Verify patch/minor/major resolution, mixed-label precedence, unlabeled PR behavior, version/lockfile consistency, and repeat runs without duplicate releases or publications.
- Update
CONTRIBUTING.mdwith the label policy and maintainer release process.
Related Files
.github/workflows/release.yml.github/workflows/publish-testpypi.ymlpyproject.tomluv.lockCONTRIBUTING.md
- Lenguaje dominante
- Python
- Estrellas
- 0
- Forks
- 4
- Merge medio
- 1 d 14 h
- PR fusionados (30 d)
- 11
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
huggingface/kernels#1006 ·
Los mantenedores suelen responder en 1 día
-
precond_kda (new op, #1552) backward kernels hit CUDA illegal memory access on Blackwell under triton 3.3.1, pass under triton 3.7.1Posiblemente ocupada @YYuJLiu la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
fla-org/flash-linear-attention#1749 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
bridgecrewio/checkov#7804 ·
Los mantenedores suelen responder en 2 días
-
area:filesystem bug need-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
Los mantenedores suelen responder en 1 día
-
triage/confirmed
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
agentscope-ai/agentscope#4068 ·
Los mantenedores suelen responder en 2 días