Release 1.2.0

Aperta
  • Qualcosa non va?
#175 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@benoit74 ci sta già lavorando.

Dal 10/11/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

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)
Lingua principale
Python
Stelle
5
Fork
4
Merge medio
1g 12h
PR unite (30g)
57

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di openzim/papers

Tutte le issue di openzim/papers

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.