Release 0.10.0

[benoit74]

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
• Adjust version in src/kiwixstorage/__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/python-storagelib/releases and tagged Latest
• Check that version is published on Pypi at https://pypi.org/project/kiwixstorage/
• 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 to x.y.z+1-dev0(next patch a priori )

[benoit74]

@elfkuzco @rgaudin shall we proceed with this 0.9.1 release so that we make changes of #12 available to the Zimfarm or do you feel like we might need more and should wait a little bit?

@elfkuzco did you confirm that this #12 PR is sufficient / OK for implementing required changes in Zimfarm by using directly the main branch in Zimfarm dependencies?

[rgaudin]

In favor of releasing

[elfkuzco]

@benoit74 , I have tested this out by disabling my internet and can confirm it works. There's an additional param not in the PR #12 retries which is a dictionary specifying max_attempts. I set it to 1 in the venv and connect_timeout of 1s fails quicker. But when I leave the retries, they are retried