Release v4.0.0

[Jaifroid]

With the new Zimit support, I think we have enough to justify a major version release in the New Year - 4.0. Although this has been released only to the browser-extension.kiwix.org (PWA) channel as a "sneak preview", I think we should capitalize on this and use it as a good reason for a v4.0.

These are the steps to complete a new release:

• Wait for some Issues / PRs to be completed (t.b.c.)
  • Use libzim for reading ZIM contents #1160 (@Rishabhg71)
  • Added String.prototype.replaceAll method #1190 (@Greeshmanth1909, but waiting on my review)
  • In Zimit archives when detecting PDFs for load in new tab, do a Header lookup before deciding a resource is external #1183
  • Do some testing with Zimit 2.0 archives before releasing v4.0 #1194
  • If Added a feature that prompts a user when a new Zim file is opened. #1192 is completed in time, then we can quickly do Rename "JQuery mode" to "safe mode"? #1197
  • Add support for Zimit v2.0 archive types #1199
  • Fix URL handling for zimit2 ZIMs in jQuery mode #1206
  • Add content warning for zimit2 in service worker local mode #1209
  • Possibly Use "Group Publisher" to publish Kiwix JS extension for Chrome #1031 (@kelson42)
• Create PR to update the changelog file
• Rename all higher milestones by incrementing their names, create a new 4.1 milestone and move open issues to this new one
• Draft the new release with desired tag
• Run Set-AppVersion script (or manually change in 6 files) the version number to v4.0.0, also run npm install to update package-lock.json, and commit
• Final tests (some can be done on https://kiwix.github.io/kiwix-js)
  • Firefox OS
  • IE11
  • Edge Legacy
  • Chromium Extension
  • Firefox Extension
• Add release date to changelog and squash/merge PR
• Publish the new release (this will create the tag and start the release workflow)
• Check that dockerfile built correctly
• Generate unsigned extensions (should be automatically triggered on GitHub Actions by the tag creation)
• Check that the PWA version was correctly set in browser-extension.kiwix.org (should be automatically triggered by tag creation)
• Upload the unsigned extensions to Stores:
  • Firefox - https://addons.mozilla.org/fr/firefox/addon/kiwix-offline/
    • Check that the minimum Firefox version is correct
  • Chrome MV3 - https://chrome.google.com/webstore/devconsole
  • Edge MV3 - https://partner.microsoft.com/en-us/dashboard/microsoftedge/
  • Ubuntu touch - https://open-store.io
• Prepare the source code for version 4.0.1 (changes should be made to 9 files, or use the Set-AppVersion script to update 8 files, followed by npm install to update package-lock.json.)
• When available, copy the signed extension binaries to https://download.kiwix.org/release/browsers/
  • Firefox - xpi downloadable from extension page
  • Chrome - crx downloadable from extension mgmt page
  • Edge - check version is published, then use direct link for Edge-specific crx
• Check that the implementation on kiwix.github.io/kiwix-js/ is synchronized automatically with main
• Publicize these new versions
• Close this issue and close the v4.0 milestone

[Jaifroid]

@kelson42 We now have unsigned extension versions for release 4.0.0! I've validated that this is uploadable to the Edge Extension store, so it should also work for the Chrome Extension store. This is the package you need:

https://download.kiwix.org/nightly/2024-02-22/kiwix-chrome-unsigned-extension-mv3-4.0.0.zip

Could you kindly upload it? I'll take care of the remaining packages (Firefox and Ubuntu). The changelog is here: https://github.com/kiwix/kiwix-js/blob/main/CHANGELOG.md .

[kelson42]

@Jaifroid I missed your message, will do that ASAP Done, waiting review.

[Jaifroid]

@kelson42 Thank you, I see it's all done!

Just waiting for MS to certify the Edge extension now.... (submitted last week!).

[Jaifroid]

All updated now.