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

Release from a tag: CI builds and publishes, with one tag style across the three libraries

Abierto
  • ¿Algo no está bien?
#158 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
38/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
github-actions, python
Área
ci-cd, devops, release

Línea de trabajo

Start by reading pyproject.toml for the project version and build configuration, then inspect the repository’s existing GitHub Actions workflows and release process. Implement and document the tag-triggered release flow described in the issue, including the version check, wheel smoke test, and trusted publishing setup. Done means a test tag completes the dry run, RELEASING.md is merged, and the required secrets or publisher configuration are documented for the maintainer.

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

Descripción

enhancement

The 0.3.0 / 3.3.0 / 0.2.0 releases were built and tagged by hand, and they drifted. drivine4j was published from main past its release PR, so its tag had to follow what was published. drivine nearly went out from a checkout with a stale node_modules. The tag styles also differ (0.3.0 in drivine4j, vX.Y.Z in the others).

The same release process for all three libraries:

  1. A release PR bumps the version and the changelog. It is reviewed and passes CI like any other PR.
  2. Merging it is the release point. The merge commit is tagged vX.Y.Z, the same style in all three repos.
  3. A tag push runs a GitHub Actions workflow that checks out the tag, runs the full gate, builds, and publishes. Nothing is built from a local checkout.
  4. Credentials live as repo secrets (or trusted publishing), never on a laptop.
  5. RELEASING.md describes the steps. Each repo has the same file, differing only in its publish step.

Done when:

  • a dry run (to a staging target or with publish skipped) works from a test tag;
  • RELEASING.md is merged;
  • the secrets are listed for the maintainer to add.

Use it for the next release, once the "Next release + 1" backlog is cleared.

drivine-python specifics:

  • Publish: uv build (hatchling), then upload to PyPI with trusted publishing (OIDC); no token needed.
  • Setup: configure a PyPI trusted publisher for the repo and workflow.
  • Check: pyproject.toml's version matches the tag, or the job fails.
  • Smoke test: after the build, install the wheel into a clean venv and run python -m drivine.stubs.
Lenguaje dominante
Python
Estrellas
1
Forks
0
Merge medio
1 h 16 min
PR fusionados (30 d)
74

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 liberation-data/drivine-python

Todos los issues de liberation-data/drivine-python

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.