Release 0.1.0

[benoit74]

• Check that code adapted from libretexts.org has not changed or not to be backported:
  • getCoverpage function in https://github.com/LibreTexts/Libretext/blob/master/public/Miscellaneous/reuse.js (adapted in get_cover_page function of client.py)
  • https://github.com/LibreTexts/Libretext/blob/master/public/DynamicLicensing/dynamicLicensing.js did not changed or that no backport is needed (adapted in detailed licensing rewrite logic)
  • https://github.com/LibreTexts/Libretext/blob/master/public/Leo%20Jayachandran/Glossarizer/libretextsGlossarizer.js did not changed (adapted in glossary rewrite logic)
  • https://github.com/LibreTexts/Libretext/blob/master/public/Leo%20Jayachandran/DynamicIndex/dynamicIndexMaker.js (adapted in index rewrite logic)
  • https://github.com/LibreTexts/Libretext/blob/master/public/DynamicTOC/dynamicTOC.js (adapted in table of content rewrite logic)
• Check that dependencies have been updated to latest version
• Check Usage (in README.md) and FAQ are still up-to-date
• Commit and push these changes to a PR and then merge to main branch
• Secure the CI is green on git main branch
• Update Github milestone to match the issues that will be released
• Close Github milestone
• Adjust version in __about__.py to x.x.x
• Update the Changelog so that it is in line with the content of Github milestone
• Commit and push these changes to tag on Github named vx.x.x
• Create a Github release, pointing to the tag, with the Changelog of this release, and 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/mindtouch/releases and tagged latest
• Check that version is published on Pypi at https://pypi.org/project/mindtouch2zim/
• Check that version is published on Github Container Registry at https://ghcr.io/openzim/mindtouch 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 version incrementaly)
• Commit and push these changes to main Github branch
• Inform rgaudin/benoit74 that a new release is ready to use so that they will update Zimfarm recipes
• Advertise the new scraper release on #scrapers Slack channel
• If needed, open a PR on Zimfarm to add support for new CLI parameters of interest

[benoit74]

I intended to release 0.1.0, but in fact this is not feasible until zimscraperlib is released as well.