Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 1.14.1 #2155

Open
17 of 21 tasks
benoit74 opened this issue Feb 10, 2025 · 1 comment
Open
17 of 21 tasks

Release 1.14.1 #2155

benoit74 opened this issue Feb 10, 2025 · 1 comment
Assignees
Labels
Milestone

Comments

@benoit74
Copy link
Contributor

benoit74 commented Feb 10, 2025

  • Check that dependencies have been updated to latest version
  • Check Usage (in README.md) and FAQ 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)
  • Review and approve release workflow at https://github.com/openzim/mwoffliner/actions
  • Check that version is published as a Github release at https://github.com/openzim/mwoffliner/releases and tagged latest
  • Check that version is published on NpmJs at https://www.npmjs.com/package/mwoffliner
  • Check that version is published on Github Container Registry at https://ghcr.io/openzim/mwoffliner 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)
@benoit74 benoit74 added the task label Feb 10, 2025
@benoit74 benoit74 added this to the 1.14.1 milestone Feb 10, 2025
@benoit74 benoit74 self-assigned this Feb 10, 2025
@benoit74 benoit74 mentioned this issue Feb 10, 2025
23 tasks
@benoit74
Copy link
Contributor Author

Formal release completed, @kelson42 I let you advertise the release once you see fit. FYI, I've already started a first batch of recipes on the Zimfarm (targetting DEV environement) to check how this works on a larger scale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant