openzim / openzim/python-scraperlib

Release 5.5.0

Offen
#309 0 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@benoit74 arbeitet bereits daran.

Seit 28.5.2026.

task
Vorherrschende Sprache
Python
Sterne
31
Forks
27
Ø Merge
3 T. 7 Std.
Gemergte PRs (30 T.)
2

Beschreibung

This issue serves as a checklist for the release event.

  • Secure the CI is green on git main
  • Check that dependencies ranges are ok, upgrade if needed (especially wombat.js in openzim.toml)
  • Ensure there is no new release on wabac.js and more specifically a change in fuzzymatcher.ts which has to be backported in rules/rules.yaml or a change in jsrewriter.ts which has to be backported in src/zimscraperlib/rewriting/js.py
  • Adjust version in src/zimscraperlib/__about__.py to x.x.x and in javascript/package.json 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/python-scraperlib/releases and tagged Latest
  • Check that version is published on Pypi at https://pypi.org/project/zimscraperlib/
  • Create a new Github milestone with the next version incrementaly (a priori a minor one)
  • 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 src/zimscraperlib/__about__.py and in javascript/package.json to x.y.z+1-dev0(next patch a priori )
  • Inform #scrapers channel on Slack about the new version

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.