Release 0.3.0
Open
@benoit74 is already working on this.
Since May 19, 2026.
task
- Dominant language
- Python
- Stars
- 19
- Forks
- 5
- Avg merge
- 4m
- Merged PRs (30d)
- 2
Description
- 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
mainbranch - Secure the CI is green on git
mainbranch - Update Github milestone to match the issues that will be released
- Close Github milestone
- Adjust version in
scraper/src/maps2zim/__about__.pytox.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/maps/releases and tagged
latest - Check that version is published on Pypi at https://pypi.org/project/maps2zim/
- Check that version is published on Github Container Registry at https://ghcr.io/openzim/maps 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
scraper/src/maps2zim/__about__.pytox.y.z+1-dev0(next patch version incrementaly) - Commit and push these changes to
mainGithub 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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.