Release 1.2.0

Abierto
  • ¿Algo no está bien?
#175 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@benoit74 ya está trabajando en esto.

Desde el 10/11/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

This issue serves as a checklist for the release event.

  • Check that dependencies have been updated to latest version (especially python-scraper lib)
  • Adjust version in __about__.py to x.x.x
  • Update Github milestone to match the issues that will be released
  • Close Github milestone
  • Update the Changelog so that it is in line with the content of Github milestone
  • Push a tag on Github named vx.x.x
  • Create a Github release, pointing to the tag, with the Changelog of this release
  • Publish the Github release (this will trigger the CI, if the CI fails and you have to push a minor fix which does not justify to create a new version, you will have to delete the release and re-create it from scratch)
  • Check that version is published as a Github release at https://github.com/openzim/papers/releases and tagged latest
  • Check that version is published on Pypi at https://pypi.org/project/papers2zim/
  • Check that version is published on Github Container Registry at https://ghcr.io/openzim/papers and tagged latest
  • Create a new Github milestone with the next minor version incrementaly
  • Create a new Github issue attached to this milestone with this checklist inside
  • Create new ## [Unreleased] section in Changelog (placeholder for future entries)
  • Adjust version in __about__.py to `x.y.z+1-dev0 (next patch release a priori)
  • Push both changes to main branch
  • Inform rgaudin/benoit74 (on #scrapers on slack) that a new release is ready to use so that they will update Zimfarm recipes (mention release version / tag name)
Lenguaje dominante
Python
Estrellas
5
Forks
4
Merge medio
1 d 12 h
PR fusionados (30 d)
57

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 openzim/papers

Todos los issues de openzim/papers

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.