3.2.0

[benoit74]

• Check that dependencies have been updated to latest version
• Check Usage (in README.md) and FAQ (Github Wiki) are still up-to-date
• Ensure the CI is green on git main
• 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
• Update version in package.json to x.x.x
• Commit and push these changes to tag on Github named vx.x.x (v prefix is mandatory)
• 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/phet/releases and tagged latest
• Check that version is published on NpmJs at https://www.npmjs.com/package/phetscraper
• Check that version is published on Github Container Registry at https://ghcr.io/openzim/phet 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 package.json 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 / remove old ones / update recipes (or ask rgaudin/benoit74 for help)